What does this skill do?

The Skill Code Verification Loop runs a structured verification workflow consisting of six phases—build, typing, lint, tests, security, and diff—to ensure that every change meets quality standards before moving forward or creating a pull request. It returns a consolidated report showing the status of each phase and the overall decision on whether the code is ready for a pull request.

Pre-PR Verification
Run all quality checks before creating a pull request and receive the readiness report.
Tests with coverage
Run the test suite, verify the minimum coverage threshold (80%), and report any failed tests.
Security Scan
Detects exposed secrets, API keys, and forgotten debug statements in the code.
Diff Review
Check the modified files for unintended changes or errors in error handling.

Usage examples

🔍 Full verification
Run the full verification loop before creating the PR: build, types, lint, tests, security, and diff.
🧪 Just tests and coverage
Run the coverage tests and let me know if we exceed the 80% threshold.
🔒 Security Scan
Check for exposed secrets, API keys, and forgotten `console.log` statements in the code before committing your changes.
📊 Check out the diff
Check the files that have changed since the last commit and let me know if there are any unintended changes or any issues with error handling.

Features

6-Step Verification Process Build, static typing, lint, tests with code coverage, security scanning, and diff review—all in a single workflow.
Consolidated Report Returns a structured report with the PASS/FAIL status for each phase and the overall READY/NOT READY decision.
Multilingual Compatible with TypeScript (tsc, ESLint) and Python (pyright, ruff, pytest) projects, among others.
Detection of Secrets Scan the code for forgotten API keys, tokens, and debug statements.
Can be incorporated into long sessions Designed to run periodically every 15 minutes or after major milestones in continuous development sessions.

Frequently asked questions

It supports TypeScript (tsc, ESLint, npm), Python (pyright, ruff, pytest), and any project that has build, lint, and test commands configured.
No. The skill uses the tools already installed in your project (tsc, ESLint, pyright, ruff, pytest, etc.). You just need to have them set up.
The report will set the overall status to "NOT READY" and list the prioritized issues so you can correct them before retrying.
Yes. You can ask Claude to run only tests, only security checks, or only the diff, depending on what you need at any given time.
Code Verification Loop — Guaranteed Quality Before Release

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.