verification-loop

Automate code change verification against user requests and acceptance criteria.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/eroslifestyle/Claude-Orchestrator-Plugin --skill verification-loop-eroslifestyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/eroslifestyle/Claude-Orchestrator-Plugin/tree/main/github-package/skills/verification-loop
Command: npx skills add https://github.com/eroslifestyle/Claude-Orchestrator-Plugin --skill verification-loop-eroslifestyle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the crucial step of verifying that implemented code changes accurately fulfill the original user request, preventing issues before delivery.

Core Features & Use Cases

  • Automated Code Validation: Checks syntax, runs tests, and matches code against requirements.
  • Regression Detection: Scans for common issues like TODOs, FIXMEs, and commented-out code.
  • Use Case: After a developer implements a new feature, this Skill runs automatically to confirm the code is clean, functional, and exactly what was asked for, before the feature is considered complete.

Quick Start

Run the verification-loop skill to check the recent code changes against the original request.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I automate code validation against user requests before delivery?

Automated code validation checks syntax, runs test suites, and matches implemented changes against original user requests and acceptance criteria. It prevents issues before delivery by executing syntax checks, pytest, and grep scans.

How does regression detection work for commented-out code and TODOs?

Regression detection scans codebases for common issues like TODOs, FIXMEs, and commented-out code using grep. It identifies leftover debugging artifacts to ensure the final implementation is clean and functional before delivery.

Can I use Python linters and pytest to verify post-implementation quality assurance?

Python linters and pytest verify post-implementation quality assurance by executing syntax checks and running test suites. They confirm code changes are functional and match acceptance criteria during pre-delivery validation workflows.

What is the best way to match code changes against acceptance criteria?

The best way to match code changes against acceptance criteria is running an automated verification loop. It validates implemented features by applying syntax checks, request matching, and regression scans to ensure exact requirement fulfillment.

When do I need to run a verification loop for code review?

You need to run a verification loop for code review after a developer implements a new feature and before it is considered complete. It confirms the code is clean, functional, and exactly what was requested during pre-delivery validation.