verification-loop

Guide code verification through success states, tests, and regression checks.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/AtlasRoX/super-fiesta --skill verification-loop-atlasrox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/AtlasRoX/super-fiesta/tree/main/skills/verification-loop
Command: npx skills add https://github.com/AtlasRoX/super-fiesta --skill verification-loop-atlasrox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need for rigorous code verification, preventing regressions and ensuring that all changes meet defined success criteria before user review.

Core Features & Use Cases

  • Define Success States: Clearly articulate expected outcomes and non-outcomes.
  • Test Creation: Generate minimal reproduction scripts for bugs or write new tests for features.
  • Execute & Observe: Run tests and meticulously analyze output for failures.
  • Regression Checking: Verify that existing functionality remains intact.
  • Self-Correction: Perform final checks for stray logs, TODOs, and style consistency.
  • Use Case: After implementing a new API endpoint, use this Skill to write a test that confirms it returns the correct data and status code, and then run existing tests to ensure no other part of the application broke.

Quick Start

Run the verification-loop skill to ensure the latest code changes are correct.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I verify code correctness and prevent regressions before a release?

To verify code correctness, implement a systematic protocol that defines success states, creates test cases, executes tests, checks for regressions, and performs self-correction to ensure all changes meet requirements.

What is the best way to ensure code changes are thoroughly validated against requirements?

The best way to validate code changes against requirements is to define clear expected outcomes and non-outcomes, generate minimal reproduction scripts, and execute tests to meticulously analyze output for failures.

How do I write tests for a new API endpoint and ensure no regressions occurred?

Write a test confirming the endpoint returns correct data and status codes, then run existing tests to verify existing functionality remains intact and no other part of the application broke.

What steps should I take to check for regressions after implementing a new feature?

To check for regressions after implementing a feature, execute existing tests to verify functionality remains intact, analyze output for failures, and perform final self-correction checks for stray logs and style consistency.

Why do I need a verification protocol for debugging and testing code?

You need a verification protocol to address the critical need for rigorous code verification, ensuring all code changes are thoroughly validated and preventing regressions before user review.