vc-autoresearch

Runs iterative find-gaps-then-fix loops against specs, tests, and docs until convergence or a metric target.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-autoresearch-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-autoresearch
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-autoresearch
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-autoresearch-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Manually re-checking a spec, test suite, or document after every fix is slow and error-prone, and it is easy to stop too early or loop forever. This Skill automates a bounded improvement loop: research agents find gaps, fix agents apply corrections, and the loop repeats until no gaps remain, a numeric metric goal is hit, or a plateau/cap/regression halt condition triggers. ## Core Features & Use Cases - Iterative gap-fix loop: Spawns parallel research agents to find FAIL/CONCERN/OBSERVATION gaps, then parallel fix agents to resolve them, with per-iteration reports and a TSV results log. - Metric-goal mode: Accepts a verify: shell command that outputs a number (e.g., lint error count, coverage percent) and loops until the target is reached, with an optional guard: command that must stay green after every fix batch. - Domain presets and subcommands: Ships canonical configs for spec, tests, ux, docs, plan, errors, and harness domains, plus probe, reason, and evals subcommands for persona interrogation, adversarial debate, and TSV trend analysis. - Use Case: Point it at a plan document with domain: plan and it runs validate-fix cycles (PVL), writing one report per iteration and stopping when the validator returns PASS or the 10-cycle cap is hit. ## Quick Start Ask the AI to run vc-autoresearch with domain spec against your requirements document and let it loop until no gaps remain.

Frequently Asked Questions about vc-autoresearch

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

FAQPage Schema
How do I run an automated fix loop until all lint errors are gone?

Invoke the loop with domain errors, your source files as the corpus, and a verify command that counts lint errors (for example an ESLint JSON count). The loop repeats research and fix cycles until the count reaches the target of zero or the iteration cap is hit.

How does the loop know when to stop iterating?

It stops on SUCCESS when agents find zero gaps for the configured consecutive iterations or the verify metric reaches its target. It also halts on plateau (no progress for 3 cycles), the hard iteration cap, or a regression where previously passing checks now fail.

What is the difference between the verify and guard commands?

The verify command measures the target metric and decides whether the goal is met. The guard command is a safety check, such as a test suite, that must pass after every fix batch; if it fails, the batch is reverted and a regression flag is logged.

Can I prevent certain files from being modified during the fix loop?

Yes, use the frozen_files parameter with a glob pattern. Any matching file is excluded from the fix corpus and fix agents must refuse to modify it, which is used for frozen specification files in the harness domain.

What happens if the metric measurement is noisy?

The references describe noise-aware verification: low-noise metrics need a single run, medium noise uses two runs with the worse result, and high-noise metrics like latency use three to five runs with the median. A min-delta threshold filters out improvements within measurement variance.