verification-loop

Run build, type, lint, test, security, and diff checks before a PR.

5|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill verification-loop-faisalalqarni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/FaisalAlqarni/sp-ecc/tree/main/skills/verification-loop
Command: npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill verification-loop-faisalalqarni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the comprehensive verification of code correctness, ensuring that builds, type checks, linting, tests, security scans, and diff reviews all pass before code is committed or merged.

Core Features & Use Cases

  • Automated Quality Gates: Runs a series of checks to ensure code meets quality standards.
  • Comprehensive Verification: Covers build, type, lint, test, security, and diff review stages.
  • Use Case: After completing a new feature, invoke this skill to get a go/no-go decision on readiness for a Pull Request, identifying any issues that need immediate attention.

Quick Start

Run the verification loop to check the correctness of your implementation.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run automated quality gates before creating a pull request?

A verification loop runs automated checks for builds, types, linting, tests, and security scans to ensure code correctness before creating a pull request. This provides a clear go/no-go decision on readiness.

What does comprehensive code verification include besides running tests?

Besides tests, comprehensive code verification includes build verification, type checking, lint checking, test execution with coverage, security scans for secrets, and a diff review.

When should I run a security scan for secrets and console logs?

A security scan for secrets and console logs should be run after completing a feature or significant code change. It is part of a verification loop invoked to ensure quality gates pass before committing code.

How can I check test suite coverage and lint rules automatically?

You can check test suite coverage and lint rules automatically by invoking a verification loop. This loop systematically verifies implementation correctness by executing the test suite with coverage and running lint checks.

What is the best way to review code diffs for quality standards?

The best way to review code diffs for quality standards is incorporating them into a verification loop. This performs an automated diff review alongside build, type, lint, test, and security checks to ensure correctness.