fm-audit-codex

Runs an independent Codex audit of migrated page artifacts as an advisory second opinion.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill fm-audit-codex-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fm-audit-codex
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/frontend-migration-plugin/skills/fm-audit-codex
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill fm-audit-codex-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When migrating legacy pages through an automated pipeline, a single model's self-review can produce false passes at each gate. This Skill runs Codex as an independent auditor over a migrated page's artifacts — analyze, plan, gen, verify, e2e, parity, and route — giving a second opinion that cross-checks Claude's own gate results without ever blocking the pipeline. ## Core Features & Use Cases - Independent stage audits: Audits any or all of the seven migration stages (analyze/plan/gen/verify/e2e/parity/route) via a dedicated codex-auditor subagent with isolated parameters. - Advisory verdicts: Records pass/concerns/fail/error/skipped verdicts with finding counts into codex-audit.json under a page lock, never changing the page's pipeline status. - Status-aware next-step guidance: When unresolved high findings exist, names exactly one remediation command based on the page's state machine status (e.g., fm-fix, fm-gen --force, fm-route --revert). - Use Case: After migrating a hotel booking page and passing all gates, run the audit with --all to get an independent review of every stage's artifacts before flipping traffic with fm-route --flag-on. ## Quick Start Run the Codex audit for the checkout page across all stages by asking to audit the migrated checkout page with fm-audit-codex.

Frequently Asked Questions about fm-audit-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an independent audit of a migrated page?▼

Invoke fm-audit-codex with the page name and optionally --stage for a single stage or --all for every stage whose inputs are available. It spawns a codex-auditor agent that records verdicts in codex-audit.json under the page's migration directory.

Does the Codex audit block the migration pipeline?▼

No, the audit is strictly advisory and never blocks. It records pass, concerns, fail, error, or skipped verdicts in codex-audit.json without changing the page's status, though fm-route --flag-on requires acknowledging unresolved findings before flipping.

What happens if the Codex CLI is not installed?▼

The auditor agent detects the missing CLI and records a skipped verdict for that stage in codex-audit.json, along with an install hint in the report. This persisted skipped state distinguishes an unavailable tool from a stage that was never audited.

Which migration stages can be audited?▼

Seven stages: analyze, plan, gen, verify, e2e, parity, and route. Verify is gated on the tracker's verifiedAt field, and route requires the page to be at parity-passed or beyond with routing artifacts prepared.

What should I do when the audit reports high findings?▼

The report names exactly one remediation command based on the page's current status, such as fm-fix for verify-failed states, fm-gen --force when regenRequiredAt is set, or fm-route --revert when a flip is live or in flight.