audit-config

Audit this repository against its own standards and report what has drifted.

Inventory

ls agents/ skills/ .claude/rules/common/ .claude/rules/_template/ 2>/dev/null
echo "--- roster ---"
grep -c "^| " .claude/rules/common/agents.md
echo "--- line counts ---"
find . -name "*.md" -not -path "./.git/*" -exec wc -l {} + | sort -rn | head -15

Checks

Run every check and report all findings — do not stop at the first one.

1. Agent roster sync

Every file in agents/ must appear in the table in .claude/rules/common/agents.md, and every row in that table must have a file. Nothing enforces this automatically, so it drifts silently. Report missing rows and orphaned rows separately.

2. Layer discipline

• Every topic file in a skills/standards-*/ layer opens with a > Extends [...] line pointing at the layer above it (common/ for a language, the language layer for a framework).
• No rule is restated from a layer above. Flag duplicated guidance by topic and quote both copies.
• Process topics (agents, code-review, development-workflow, git-workflow) appear only in common/.

3. Frontmatter

• Files in .claude/rules/common/ have no frontmatter — that is what makes them load unconditionally.
• Every SKILL.md has name and description. The name matches its directory.
• Skills with side effects (commits, scaffolding, deploys) set disable-model-invocation: true.
• Skills using context: fork name an agent, and the agent exists.

4. Links

Every relative markdown link resolves to a file that exists. Check CLAUDE.md, the rules, the skills, and the docs. Report each broken link with its source file and line.

Two exclusions, both deliberate:

• .claude/rules/_template/ — its links are written for the destination a copy lands in (skills/standards-<layer>/), so they do not resolve from the template directory by design.
• Anything inside a code span or fenced block — those are illustrations of what to write, not links.

5. Size limits

The repository applies its own standard to itself: markdown files ≤800 lines. Flag anything over, and anything approaching it, with a suggested split.

6. Documentation parity

README.md and README.ru.md must cover the same sections in the same order. Report sections present in one and missing from the other. Same for docs/ and docs/ru/.

7. Claims match reality

Flag any place the documentation describes something that does not exist — a file listed in a directory map that is absent, a command referenced that is not wired, a topic named as shipped that was never written.

Output

Group findings by check, ordered by severity:

• CRITICAL — the config is broken or silently inactive (a rule that never loads, a skill that cannot resolve).
• HIGH — drift that misleads a reader (unregistered agent, docs describing something absent).
• MEDIUM — maintainability (duplication across layers, oversized file).
• LOW — cosmetic.

Give each finding a file path, a line where applicable, and the concrete fix. End with a one-line verdict: clean, or the count at each severity.