vibe-spec-vs-code-audit
Compares specification documents against implementation code to find divergences. Use when implementation of a spec or design doc is claimed complete.
npx skills add majiayu000/claude-skill-registry --skill spec-vs-code-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# vibe-spec-vs-code-audit Specs drift from code. Code drifts from specs. This skill catches the gaps. ## When to Use This Skill - Implementation of a spec/design doc is claimed complete - After a major refactor that should still conform to a spec - During periodic compliance checks - When debugging unexpected behavior (maybe the code doesn't match the spec) ## When NOT to Use This Skill - No spec or design doc exists (nothing to compare against) - The spec is explicitly marked as aspirational/future - Code was intentionally diverged with documented reasons ## Steps 1. **Identify the spec** — Find the specification document (design doc, PRD section, API spec, etc.) 2. **Identify the implementation** — Find the code files that implement this spec 3. **Line-by-line comparison** — For each requirement/section in the spec: - Find the corresponding code - Check: Does the code match the spec exactly? - If divergent: Record as a GAP 4. **Classify each gap**: - **ID**: GAP-[section]-[number] (e.g., GAP-AUTH-001) - **Type**: Missing (spec says X, code has nothing) / Incorrect (spec says X, code does Y) / Extra (code has X, spec doesn't mention it) - **Severity**: Critical (breaks core functi
- When to Use This Skill
- When NOT to Use This Skill
- Steps
- Output Format
- Spec vs Code Audit
- Top 3 Risks
- Recommended Fix Order
What does the vibe-spec-vs-code-audit skill do?
Compares specification documents against implementation code to find divergences. Use when implementation of a spec or design doc is claimed complete.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill spec-vs-code-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.