vibe-validate

Use when starting vibe-validate work or picking a sub-skill. Router for the validate/fix loop, project setup, cache and locking, work recovery, extractor authoring, PR/CI monitoring, and non-Claude agent integration.

Use when monitoring PR/CI status after pushing, diagnosing CI failures, investigating flakes, or cleaning up merged branches. Triggers on watch-pr, CI checks, CI debug, PR status, merged-branch cleanup.

Use when validation fails but no errors are extracted, or when writing a custom error extractor for a tool vibe-validate does not recognize. Covers built-in extractors, vv create-extractor, and the plugin system.

Use when debugging cache misses, unexpected cache hits, or concurrency lock conflicts. Covers the git tree hash caching model, lock scopes, --no-lock, --no-wait, and the vv cleanup-temp maintenance utility.

Use when wiring vibe-validate into a non-Claude AI coding assistant (Cursor, Aider, Continue, or any other tool). Covers system-prompt additions, command wrappers, and output routing for agentic workflows.

Use when recovering lost work — accidentally deleted file, git restore wiped changes, failed rebase, editor crash, or branch switch lost untracked files. Covers vv history, vv snapshot, tree-hash recovery with git cat-file and git checkout.

Use when bootstrapping vibe-validate in a new repo, adjusting the config, or diagnosing setup. Covers vv init, vv doctor, vv config, templates, heterogeneous-language setup, generate-workflow, and dependency-lock-check.

Use when running validation during day-to-day coding — vv validate, vv pre-commit, vv state, vv run. Covers the iterate-fix-revalidate loop, cached state queries, and command wrapping for LLM-optimized error extraction.