vc-followup

Audit agent-delivered work with loctree, semgrep, and cargo clippy checks.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/VetCoders/vibecrafted --skill vc-followup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-followup
Source: https://github.com/VetCoders/vibecrafted/tree/main/skills/vc-followup
Command: npx skills add https://github.com/VetCoders/vibecrafted --skill vc-followup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-implementation follow-up audits of agent-delivered work, surfacing implementation gaps, readiness risks, and actionable next steps to close gaps before hands-on build or testing.

Core Features & Use Cases

  • Enforces a fixed audit sequence: vc-init -> vc-workflow -> vc-agents -> synthesis, ensuring no steps are skipped.
  • Aggregates findings by severity and delivers concrete next actions to drive remediation.
  • Use Case: after an agent-driven release, run this skill to obtain a consolidated readiness verdict and prioritized fixes.

Quick Start

Instruct vc-followup to execute the standard post-implementation audit on the target repository and return a concise synthesis.

Frequently Asked Questions about vc-followup

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

FAQPage Schema
How do I audit agent-delivered code for readiness risks before testing?

To audit agent-delivered code for readiness risks, run a post-implementation follow-up audit that surfaces implementation gaps and actionable next steps. This aggregates findings by severity and enforces required gates like semgrep security checks, culminating in a consolidated GO/NO-GO verdict.

What is a GO/NO-GO verdict in automated software review workflows?

A GO/NO-GO verdict in automated software review workflows is a consolidated readiness decision based on synthesized audit findings. It aggregates severity-ranked gaps from required gates to determine whether agent-delivered output is ready for hands-on build or testing.

How do I enforce security and quality gates like semgrep and cargo clippy in an agent workflow?

To enforce security and quality gates like semgrep and cargo clippy in an agent workflow, apply a fixed audit sequence that runs these checks as mandatory artifacts. This ensures no steps are skipped and delivers concrete next actions to drive remediation of any surfaced risks.

Can I run a post-implementation audit if previous agent workflow steps were skipped?

You cannot run a complete post-implementation audit if previous steps were skipped. The audit enforces a fixed sequence requiring vc-init, vc-workflow, and vc-agents outputs to synthesize findings and produce a consolidated readiness verdict with prioritized fixes.

How do I synthesize findings from multiple agent code generation tasks?

To synthesize findings from multiple agent code generation tasks, apply an end-to-end review pipeline that aggregates outputs by severity. This process surfaces implementation gaps and delivers concrete next actions to close them before hands-on build or testing begins.

When do I need a post-implementation audit chain for agent work?

You need a post-implementation audit chain for agent work after an agent-driven release produces output requiring synthesis and risk assessment. It enforces mandatory gates like loctree MCP exploration to surface readiness risks and provide prioritized findings before testing.