vc:audit-vc
The vc:audit-vc skill validates internal consistency across Claude agents, Codex configuration, README documentation, protocol files, skill discovery, seed data, and kit portability. Use it when deploying or modifying agent harnesses to ensure all configuration layers remain synchronized and correctly wired across different agent platforms and documentation systems.
git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit /tmp/vc-audit-vc && cp -r /tmp/vc-audit-vc/.claude/skills/vc-audit-vc ~/.claude/skills/vc-audit-vcSKILL.md
# Audit VC (Version Control Harness Health) Use this skill to verify that the agent harness layer is internally consistent and correctly wired across Claude, Codex, README.md, and protocol files. For context routing, grouping, and discoverability audits, use the `audit-context` skill instead. ## Workflow 1. Run the Claude/Codex agent parity validator: ```bash node .claude/skills/vc-audit-vc/scripts/validate-agent-parity.mjs ``` 2. Run the shared skill discovery validator: ```bash node .claude/skills/vc-audit-vc/scripts/validate-skills.mjs ``` 3. Run the README.md sync validator: ```bash node .claude/skills/vc-audit-vc/scripts/validate-guide-sync.mjs ``` 4. Run the protocol wiring validator: ```bash node .claude/skills/vc-audit-vc/scripts/validate-protocol-wiring.mjs ``` 5. Run the seed file consistency validator: ```bash node .claude/skills/vc-audit-vc/scripts/validate-seeds.mjs ``` 6. Run the kit portability validator: ```bash node .claude/skills/vc-audit-vc/scripts/validate-kit-portability.mjs ``` 7. If any script reports failures, inspect the referenced files and patch the smallest relevant surface. 8. Re-run the failed validators until they pass. ## Rules - Treat `.claude/agents/` as canonical for agent definitions; `.codex/agents/` mirrors them. - Treat `.claude/skills/` as canonical for skills; `.agents/skills/` is the Codex discovery symlink. - 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. - For context routing and discoverability audits, delegate to `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.