skills.rest
Chau165
Chau165COMMUNITY
Explore all skills by this author →
GitHub

verification-loop

Runs build, type, lint, test, security, and diff checks to produce a verification report.

Updated Jul 22, 2026
Search Tags:#code quality#testing#verification#coverage#lint#type check#pre-pr review
One-click install
npx skills add https://github.com/Chau165/local_skill --skill verification-loop-chau165
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/Chau165/local_skill/tree/main/plugins/ecc/skills/verification-loop
Command: npx skills add https://github.com/Chau165/local_skill --skill verification-loop-chau165

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a feature or refactor, developers often skip systematic quality checks and push code that fails builds, breaks types, or leaks secrets. This Skill enforces a structured multi-phase verification pass before a PR is created. ## Core Features & Use Cases - Six-Phase Verification: Sequentially runs build, type check (tsc/pyright), lint (npm lint/ruff), test suite with coverage, security scans for secrets and console.log, and git diff review. - Standardized Report: Produces a PASS/FAIL verification report summarizing each phase, coverage percentage, and an overall READY/NOT READY verdict for the PR. - Continuous Mode: Supports periodic re-verification during long sessions, complementing PostToolUse hooks with deeper review. - Use Case: After refactoring a TypeScript module, invoke the skill to confirm the build passes, tests meet the 80% coverage target, no API keys were committed, and the diff contains only intended changes. ## Quick Start Run the verification loop on my current changes and tell me whether the code 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 quality before creating a pull request?▼

Run a verification loop that checks build success, type errors, lint warnings, test results with coverage, and security issues, then reviews the git diff. The skill outputs a report with an overall READY or NOT READY verdict for the PR.

What checks should run after refactoring TypeScript code?▼

Run npm run build, npx tsc --noEmit for type errors, npm run lint, and the test suite with coverage targeting 80% minimum. Also scan for leaked secrets and leftover console.log statements before reviewing the diff.

Does this verification workflow support Python projects?▼

Yes, the type check phase uses pyright and the lint phase uses ruff for Python codebases. Build and test commands can be adapted to the project's Python tooling while keeping the same phase structure.

How do I check for accidentally committed API keys or secrets?▼

The security phase greps source files for patterns like sk- and api_key across TypeScript and JavaScript files. It also flags console.log statements that may leak sensitive runtime data.

When should I stop the verification loop and fix issues first?▼

Stop immediately if the build phase fails, since later phases depend on a compiling project. Critical type errors should also be fixed before continuing to lint, test, and security phases.

Related Skills

Explore More Software Engineering Skills→
arbiterForgearbiterForge
139

commit-gate

Enforce a nine-phase commit workflow with tests, linting, and secrets scanning.

Official
Advanced
DisentinelDisentinel
36

/approve — Push PR to Auto-Merge

Push a feature branch, create a GitHub pull request, and enable auto-merge.

Community
Advanced
D0NMEGAD0NMEGA
8

plankton-code-quality

Automate formatting and linting on file edits via PostToolUse hooks.

Community
Advanced
buildworksaibuildworksai

devops-cicd

Configure GitHub Actions, Docker Compose, and Kubernetes CI/CD pipelines.

Community
Advanced