vc-autoresearch

Runs iterative find-gaps, fix, and re-verify loops until convergence or a metric target is reached.

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-autoresearch-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-autoresearch
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-autoresearch
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-autoresearch-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Manually iterating on specs, tests, docs, or plans to find and fix gaps is slow and untracked. This Skill automates the loop: research agents find gaps, fix agents apply corrections, and a bookkeeping layer tracks iterations, plateaus, and regressions until no gaps remain or a metric goal is hit. ## Core Features & Use Cases - Iterative Gap-Fix Loop: Spawns parallel research and fix agents per cycle, with severity floors, convergence checks, and hard termination states (SUCCESS, HALT_PLATEAU, HALT_CAP, HALT_REGRESSION). - PVL/EVL Wiring: Serves as the shared bookkeeping layer for plan-validate-fix and execute-validate-fix loops, with per-cycle reports and TSV logging. - Metric-Driven Mode: Accepts a verify command and numeric target so loops stop when coverage, lint errors, or latency goals are reached, with guard commands preventing regressions. - Use Case: Run it with domain tests and a coverage verify command to keep adding test cases until coverage hits the target, with pnpm test as a guard so no fix batch breaks the suite. ## Quick Start Ask the agent to harden a spec or improve test coverage by running vc-autoresearch with a domain, corpus paths, and an optional verify command and target.

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 iterative gap-fix loop on a spec or test suite?

Invoke vc-autoresearch with a domain (spec, tests, ux, docs, plan, or errors), corpus file paths, and optionally a verify command with a numeric target. The loop spawns research agents to find gaps and fix agents to resolve them, repeating until no gaps remain or the target is hit.

How do I improve test coverage automatically until a target is reached?

Set domain to tests, point the corpus at your source files, and provide a verify command that prints the coverage percentage plus a target value. The loop keeps adding tests each iteration until coverage reaches the target, with pnpm test as the default guard.

When does the autoresearch loop stop iterating?

The loop stops on SUCCESS when agents find no gaps for the configured consecutive iterations or the metric target is reached. It also halts on plateau (no progress for 3 cycles), the max-iteration cap, or a regression where previously passing checks now fail.

Can I prevent the loop from modifying certain files?

Yes, use the frozen_files parameter with glob patterns to exclude files from the fix corpus. Fix agents must never modify files matching those patterns, and the harness domain uses this to protect frozen spec files.

What is the difference between PVL and EVL wiring in this loop?

PVL (plan-validate-fix) uses domain plan with a validate agent running gates against a plan document until it passes. EVL (execute-validate-fix) uses domain tests where a tester agent runs contract gate commands after execution, and failing gates trigger execute-fix agents.

Why did my loop halt with HALT_PLATEAU?

HALT_PLATEAU means the gaps_found count stayed flat or increased for 3 consecutive iterations, indicating no progress. Review the results.tsv trend with the evals subcommand and consider changing the corpus scope, fix strategy, or severity floor.