메뉴
Audit and repair Pharos documentation against the codebase. Use for documentation update passes, verified-doc drift, source-path/doc-sync failures, methodology/doc routing updates, or requests to verify docs without trusting existing prose.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pharos-docs-sync-audit |
| description | Audit and repair Pharos documentation against the codebase. Use for documentation update passes, verified-doc drift, source-path/doc-sync failures, methodology/doc routing updates, or requests to verify docs without trusting existing prose. |
| user_invocable | true |
Use this skill from the Pharos repository root when the user asks to:
check:doc-source-paths, check:doc-sync, or check:verified-doc-linksdocs/agent-task-router.md and read only the docs for the matched task family.docs/doc-ownership.json to decide which docs may need updates./docs/ and README.md as the verified documentation corpus. Do not create committed planning archives.AGENTS.md and CLAUDE.md, or move it into docs/process/* and reference it from both./methodology, the owning methodology doc, and the structured entry under shared/data/methodology-changelogs/.v5.9, use v5.91 or v6.0, not v5.10.docs/agent-task-router.mddocs/process/agent-artifacts.mddocs/doc-ownership.jsondocs/testing.mdFor skill changes, also read the "Agent Skills" section of docs/process/agent-artifacts.md.
Classify the docs request:
Use:
node scripts/ci/pharos-change-contract.mjs
or --staged when auditing staged changes.
For each doc claim, inspect the source that owns the behavior:
src/app/**, src/components/**, src/lib/page-metadata.tsshared/lib/api-endpoints/**, worker/src/routes/**, worker/src/api/**shared/lib/cron-jobs.ts, shared/lib/scheduled-runner-registry.ts, worker/src/cron/**shared/data/stablecoins/coins/*.json, shared/lib/stablecoins/schema.tspackage.json, scripts/**, .github/workflows/**shared/lib/**, shared/data/methodology-changelogs/**, and route methodology sectionsPrefer source-backed corrections over prose polish.
Update the smallest set of verified docs. Remove stale claims rather than adding caveats around false text.
Common doc destinations:
docs/README.mddocs/architecture.md for structural routing/runtime model changesdocs/testing.md, docs/deployment-process.md, docs/scripts.md for CI/release behaviordocs/process/* for durable agent/operator processREADME.md, AGENTS.md, and CLAUDE.md only when top-level guidance actually changesRun the relevant doc checks:
npm run check:doc-source-paths
npm run check:verified-doc-links
npm run check:doc-sync
npm run check:agent-doc-sync
npm run check:agent-skill-symlinks
For generated docs/API artifacts:
npm run check:generated-artifacts
npm run check:docs-api-reference
npm run check:openapi
npm run check:postman
For broad docs work, prefer the specific failing check first, then npm run validate:prebuild if the user asked for production readiness.
For a broad docs-vs-code audit in Claude Code, use .claude/workflows/docs-maintenance.mjs. Its default mode verifies and adjudicates the corpus; pass mode: "remediate" to apply grouped, adjudicated fixes.
In Codex, or for a narrower family-scoped pass, use references/subagents.md to split the audit by docs family. Subagents should be read-only unless assigned a narrow doc write set.
The parent agent owns final edits, de-duplication, and validation.
Report:
Diagnose and fix failed Pharos GitHub Actions, merge-gate, deploy-cloudflare, pages-release, or rebuild-pages runs. Use when a workflow failed, a push/merge gate fails, or the user asks to retrigger and iterate until CI/deploy clears.
Run the standard Pharos release path when asked to commit in logical/thematic batches, publish through the protected main pull-request gate, or watch the production deployment. Use for release prep, final publish, deployment monitoring, and production handoff after local work is complete.
Generate a weekly changelog entry from git history. Collects commits for a date range, filters noise, clusters by theme, writes an editorial summary, and outputs a ChangelogEntry file. Default behavior stops for review; pass --commit to also commit.
Coordinate the full Pharos stablecoin addition process from eligibility through validation. Use when adding a new tracked stablecoin, promoting a pre-launch asset, or auditing whether an addition is complete.
Drain the Pharos Yield Intelligence coverage-audit queue into reviewed source coverage, documented intentional gaps, or watchlisted deferrals. Use monthly after `yield-coverage-audit` runs, after yield coverage drops, or when promoting queue candidates such as `native-exact-pool`, `lending-allowlist`, `source-family-adapter`, `stale-auto-lending-override`, or `quarantine-ready-to-restore`.
Use when asked to update pre-launch stablecoin data, add milestones, refresh launch phases, or check for promotions. Runs weekly to keep the upcoming stablecoins module current.