vc:audit-context
vc:audit-context validates the discoverability and organization of a project's context routing layer, shared skill surfaces, and Claude/Codex wiring by running a series of validators that check context discovery, skill routing coverage, cross-references, dependencies, and confusable skills. Use this skill when context documentation moves, skills are added or reorganized, or routing between agents and shared skills becomes unclear or fragmented.
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit /tmp/vc-audit-context && cp -r /tmp/vc-audit-context/.claude/skills/vc-audit-context ~/.claude/skills/vc-audit-contextSKILL.md
# Audit Context Use this skill to verify that the project's durable context layer is discoverable and organized. Optional input: a context group, agent, skill, or folder scope to prioritize during the audit. ## Workflow 1. Read `process/context/all-context.md` for the context routing protocol. 2. Read `references/audit-context.md` for the full audit process. 3. Run the context discovery validator: ```bash node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs ``` 4. Run the shared skill routing coverage validator: ```bash node .claude/skills/vc-audit-context/scripts/validate-skill-routing.mjs ``` 5. Run the skill cross-reference validator: ```bash node .claude/skills/vc-audit-context/scripts/validate-skill-cross-refs.mjs ``` 6. Run the skill dependency/confusable analysis: ```bash node .claude/skills/vc-audit-context/scripts/validate-skill-dependencies.mjs node .claude/skills/vc-audit-context/scripts/validate-confusable-skills.mjs ``` 7. Regenerate or check the machine-readable skill catalog: ```bash node .claude/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --write node .claude/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --check ``` 8. If any script reports failures, inspect the referenced files and patch the smallest relevant surface. 9. Re-run the failed validators until they pass. For agent/skill harness validation (agent parity, skill frontmatter, README.md sync, protocol wiring), use the `audit-vc` skill. ## Rules - Treat `.claude/skills/` as canonical; `.agents/skills/` is the Codex discovery symlink. - Treat `.claude/skills/vc-audit-context/references/skill-routing-policy.json` as the explicit allowlist for intentionally non-routed shared skills. - Do not move large context files without updating `process/context/all-context.md`. - Do not delete compatibility wrappers unless no current reference points to them. - Keep context groups durable-domain based, not one group per temporary feature. - When updating agents, mirror Claude markdown and Codex TOML surfaces together. - Treat validator warnings as audit findings unless the user asks for a strict cleanup. - Prefer validator-backed routing truth over adding more soft prose. - Treat process/context/generated-skills-catalog.json as the machine-readable catalog owned by `audit-context`.
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples:\n\n<example>\nContext: The user needs to investigate why an API endpoint is returning 500 errors.\nuser: "The /api/users endpoint is throwing 500 errors"\nassistant: "I''ll use the debugger agent to investigate this issue"\n<commentary>\nSince this involves investigating an issue, use the Task tool to launch the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to analyze why the CI/CD pipeline is failing.\nuser: "The GitHub Actions workflow keeps failing on the test step"\nassistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue"\n<commentary>\nThis requires analyzing CI/CD logs and test failures, so use the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user notices performance degradation in the application.\nuser: "The application response times have increased by 300% since yesterday"\nassistant: "I''ll launch the debugger agent to analyze system behavior and identify performance bottlenecks"\n<commentary>\nPerformance analysis and bottleneck identification requires the debugger agent.\n</commentary>\n</example>
EXECUTE MODE - Implementing EXACTLY what was planned. Full tool access. Can only be invoked after explicit user confirmation. Use after plan is approved.
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + INNOVATE + PLAN) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features/*/active/ only. Use after approach is decided.