vibe-validate

Route users to the correct vibe-validate sub-skill for tailored validation workflows.

3|Updated Oct 16, 2025
One-click install
npx skills add https://github.com/jdutton/vibe-validate --skill vibe-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-validate
Source: https://github.com/jdutton/vibe-validate/tree/main/docs/skills/vibe-validate
Command: npx skills add https://github.com/jdutton/vibe-validate --skill vibe-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route users to the correct vibe-validate sub-skill to tailor the validation workflow.

Core Features & Use Cases

  • Load the appropriate sub-skill that matches the current task (e.g., vv-validate-dev-loop, setting-up-projects, caching-and-locking, recovering-work).
  • Centralizes orchestration for vibe-validate lifecycle steps: init, doctor, generate-workflow, validate, state, watch-pr, and non-Claude integrations.
  • Keeps the router lightweight while delegating heavy logic to the chosen sub-skill.

Quick Start

Load the sub-skill that matches your workflow, for example 'vibe-validate:vv-validate-dev-loop'.

Frequently Asked Questions about vibe-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route AI agent validation workflows for a multi-language monorepo?

You can route AI agent validation workflows for a multi-language monorepo by loading a lightweight router that delegates heavy logic to the appropriate validation sub-skill, tailoring the process to your specific project setup.

What is sub-skill loading for CLI orchestration and when do I need it?

Sub-skill loading for CLI orchestration is a mechanism that dynamically matches your current task to a specific validation loop. You need it to seamlessly integrate on-demand lifecycle steps like init, validate, and watch-pr without overloading the main router.

Can I use this validation router with non-Claude AI agents?

Yes, you can use this validation router with non-Claude AI agents. The orchestration system explicitly supports non-Claude agent integration, allowing diverse AI agents to leverage the centralized validation and caching workflows.

How do I set up caching and locking for AI validation loops?

You set up caching and locking by loading the dedicated caching-and-locking sub-skill through the router. This tailors the validation workflow to manage state and fast caching efficiently across your monorepo projects.

Does this routing approach work for PR and CI monitoring?

Yes, this routing approach works for PR and CI monitoring. The orchestration lifecycle includes a dedicated watch-pr step, enabling you to monitor pull requests and integrate validation checks directly into your continuous integration pipelines.

What's the best way to recover work after an interrupted AI validation task?

The best way to recover work after an interrupted AI validation task is to load the recovering-work sub-skill. This routes you to the specific logic needed to restore state and resume the orchestration workflow seamlessly.