verification-loop

Automates multi-phase code quality verification including builds, linting, and testing before pull request creation.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/acta0724/claude-marketplace --skill verification-loop-acta0724
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/acta0724/claude-marketplace/tree/main/wf/skills/verification-loop
Command: npx skills add https://github.com/acta0724/claude-marketplace --skill verification-loop-acta0724

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the crucial quality checks (build, type, lint, test, security, diff) that must be performed after implementation and before creating a Pull Request, preventing the introduction of bugs and ensuring a higher standard of code.

Core Features & Use Cases

  • Comprehensive Quality Gates: Executes build, type checking, linting, and testing.
  • Security Vulnerability Scan: Checks for hardcoded secrets, debug statements, and commented-out code.
  • Code Change Review: Provides a summary of code modifications via git diff --stat.
  • Use Case: After completing a feature implementation, this Skill runs automatically to verify the code's integrity, catch potential issues, and confirm that the changes are as intended before submitting for review.

Quick Start

Run the verification-loop skill to perform all quality checks on the current implementation.

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 quality checks before a pull request?

Automating code quality checks before a pull request involves executing build, type checking, linting, and testing phases. This verification process catches potential issues and confirms changes are intended before code review submission.

Can I scan for security vulnerabilities and hardcoded secrets in my code?

Scanning for security vulnerabilities detects hardcoded secrets, debug statements, and commented-out code within your changes. This security review identifies potential risks during the automated verification process before pull request creation.

What is the best way to review code differences before submitting a PR?

Reviewing code differences before submitting a PR is best achieved by generating a summary of code modifications using git diff --stat. This change review confirms that modifications align with intended implementation goals.

Does the verification process support projects with various build tools and testing frameworks?

Yes, the verification process supports projects with various build tools and testing frameworks. It executes comprehensive quality gates across different environments to validate build, type checking, linting, and testing phases.

When do I need to run a multi-phase code verification loop?

A multi-phase code verification loop is needed after completing a feature implementation and before creating a pull request. It verifies code integrity, catches potential issues, and ensures higher standards before review.