Quality

Verification Before Completion requires a fresh falsifying check and explicit evidence before claiming work is complete, fixed, or ready to hand off. Use it when preparing to commit, merge, publish, release, or otherwise declare success.

Audit Context verifies context routing, shared-skill discoverability, and Claude/Codex wiring. Use it when context docs, skill surfaces, or routing rules move, split, or drift.

Audit Plans reviews active plan files for staleness, completion, and routing truth. Use it when cleaning up plans, reconciling active work, or archiving completed artifacts.

Audit VC verifies agent harness wiring across Claude, Codex, README.md, and protocol files. Use it when agents, skills, or development-protocol files move, split, or drift.

Debugging & System Investigation guides systematic root-cause analysis for bugs, test failures, CI issues, performance problems, and other unexpected behavior before applying fixes. It also covers log analysis, verification, and frontend checks when needed.

Feasibility Test runs a one-shot probe to check whether an unverified runtime, library, or external mechanism actually works as assumed. Use it before locking a design when the answer depends on live behavior.

Risk Evidence Pack defines the manual-first artifact set required before finalizing high-risk work. Use it to capture risk classification, code evidence, verification results, review decisions, and adversarial checks.

Scenario Explorer generates edge cases and test scenarios by decomposing a feature across 12 dimensions. Use it before implementation or testing to surface risks, failures, and coverage gaps early.

Vc Auto Research runs a find-gaps, fix, and recheck loop for specs, tests, docs, and UX hardening. Use it when you want repeated verification until no gaps remain or a metric target is reached.

Code Review Expert reviews current git changes for SOLID issues, security risks, and code quality problems. Use it when you need a senior-style review and actionable fix suggestions before merging.

Code Health Check analyzes a codebase for file organization, error handling, security basics, code quality, and dependency hygiene. Use it when you need a structured health report with issues ranked by severity.

Code Review reviews code for quality, security, performance, and maintainability. Use it when you need feedback on changes, want to check best practices, or are asking for a code review.