verification-loop

Runs build, type check, lint, tests, security scan, and diff review before pull requests.

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill verification-loop-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/verification-loop
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill verification-loop-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code changes often ship with undetected build failures, type errors, lint violations, failing tests, or leaked secrets. This Skill enforces a structured quality gate so every change is verified across six phases before a PR is created. ## Core Features & Use Cases - Six-Phase Verification: Sequentially runs build, type check, lint, test suite with coverage, security scan for secrets and debug statements, and git diff review. - Stack-Adaptive Commands: Detects Python (uv, pytest, ruff, pyright) versus Node.js/TypeScript (npm, pnpm, tsc) projects and selects the appropriate commands via a stack-detection reference. - Standardized Report: Produces a PASS/FAIL verification report with an overall READY/NOT READY verdict and a list of issues to fix. - Use Case: After refactoring a Python service, ask for verification to confirm the build passes, pytest coverage holds, no API keys leaked into the diff, and the change is ready for PR. ## Quick Start Ask the assistant to run the verification loop on the current changes and report whether the branch is ready for a PR.

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

Run a verification loop covering build, type check, lint, tests, security scan, and diff review in sequence. Each phase must pass before continuing, and the final report states whether the branch is ready for a PR.

What checks should a code quality verification pipeline include?

A solid pipeline includes build verification, static type checking, linting, a test suite with coverage reporting, a security scan for leaked secrets and debug statements, and a manual review of the git diff for unintended changes.

Does the verification loop work for both Python and Node.js projects?

Yes, it adapts commands per stack using a stack-detection reference. Python repos use uv, pytest, ruff, and pyright, while Node.js/TypeScript repos use npm or pnpm with tsc, matching the package manager already in the repo.

How do I scan code for leaked API keys and secrets?

Grep the source tree for patterns like sk- and api_key across Python and TypeScript files, and run pip-audit for Python dependency vulnerabilities. Also check for leftover print or console.log debug statements before committing.

When should I run verification during a long coding session?

Run it after completing each function or component, after major changes, and always before creating a PR. For long sessions, a checkpoint roughly every 15 minutes keeps failures small and easy to diagnose.