verification-loop

Run end-to-end code verification covering builds, types, lint, tests, security, and diffs.

Updated Feb 5, 2026

Search Tags:#testing #verification #code-quality #lint #continuous-integration #type-check #security-scan

Ready to run

npx skills add https://github.com/gugug168/claudecode-tutorial --skill verification-loop-gugug168

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/gugug168/claudecode-tutorial/tree/main/everything-claude-code-learning/02-Skills/verification-loop
Command: npx skills add https://github.com/gugug168/claudecode-tutorial --skill verification-loop-gugug168

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates and standardizes end-to-end verification after code changes to catch build failures, type regressions, lint issues, test failures, security findings, and unexpected diffs before creating a pull request.

Core Features & Use Cases

Build verification: run project builds and surface failures.
Type checking: execute TypeScript or Python static checks and report errors.
Linting and tests: run linters and test suites with coverage reporting and thresholds.
Security scans and diff review: search for secrets and debug artifacts and summarize file changes.
Use Case: Run after implementing a feature, before opening a PR, or periodically during long development sessions to produce a consolidated validation report.

Quick Start

Run the verification loop and generate a validation report summarizing build, types, lint, tests, security, and diff status.

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 verification before creating a pull request?▼

Automate code verification before a PR by running a consolidated validation loop that checks builds, types, lint, tests, and security. This process surfaces failures and unexpected diffs early, ensuring code quality before review.

What is the best way to run type checking and linting during local development?▼

Run type checking and linting locally by executing static analysis for TypeScript or Python alongside linters. This mechanism reports type errors and style issues immediately, providing a validation report without waiting for continuous integration.

Does pre-PR security scanning detect secrets and debug artifacts in my codebase?▼

Pre-PR security scanning does detect secrets and debug artifacts by searching file changes during the verification process. It flags these findings in the consolidated report, preventing sensitive data from reaching your pull requests.

Can I run continuous integration checks periodically during long-running development sessions?▼

You can run continuous integration checks periodically during long sessions to catch build regressions and test failures. This periodic validation ensures ongoing code quality and summarizes file diffs without manually triggering full pipelines.

How do I enforce test coverage thresholds when running tests before a pull request?▼

Enforce test coverage thresholds by running your test suite through the verification loop, which evaluates coverage metrics against defined limits. This process reports regressions and blocks progression if coverage drops below the required threshold.