Sumi-Docs-MCP: Skill for Codex

Audit Sumi Docs

Return one compact, findings-first audit of the live target. Treat the audit as read-only: do not modify source, configuration, Git state, GitHub state, or host state; do not install or update tools. Repository validation may refresh only its normal ignored build outputs. Return the report to the caller by default. Write a report only when the user names an ignored artifacts/ destination.

Bind the evidence snapshot

Read the root and nearest nested AGENTS.md before selecting checks. Resolve the target rather than inferring it from an earlier report:

git rev-parse --show-toplevel
git rev-parse HEAD
git branch --show-current
git status --porcelain=v2 --branch
node --version
pnpm --version

Record the UTC timestamp, operating system, target path, HEAD, branch, tree cleanliness, tool versions, commands, exit codes, and skipped checks. Inspect staged, unstaged, and untracked paths when the tree is dirty. Attribute results to HEAD only for a clean tree; otherwise identify the audited snapshot as HEAD plus the listed worktree changes and keep commit evidence separate from worktree evidence.

Use current source, tests, generated artifact contents, GitHub checks, and live probes in that order of relevance. Treat docs/history/ and package history snapshots as non-authoritative. Redact secret values and machine-specific absolute paths from the report.

Select the audit profile

• For a repository health audit, cover every applicable ownership boundary and run the root validation gates.
• For a release-candidate audit, also bind the candidate commit and artifacts, inspect the current candidate workflow and public checks, and verify the packaging, compliance, performance, publication, and rollback evidence that the candidate claims.
• For an architecture consistency audit, trace each affected contract from its authority through generated projections, consumers, tests, and operational documentation. Do not replace runtime evidence with an architecture diagram.
• For a PR, commit, or branch diff, use $sumi-docs-pr. For a security-only scan, use the available security audit workflow. For a single failure, run a focused diagnosis rather than expanding it into a repository audit.