skills.rest
CMiller838
CMiller838COMMUNITY
Explore all skills by this author →
GitHub

verification-loop

Runs build, type, lint, test, security, and diff checks to verify code changes before PRs.

Updated Sep 3, 2026
Search Tags:#testing#code review#verification#quality gates#lint#ci#type check
One-click install
npx skills add https://github.com/CMiller838/meal-planner --skill verification-loop-cmiller838
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/CMiller838/meal-planner/tree/main/.claude/skills/verification-loop
Command: npx skills add https://github.com/CMiller838/meal-planner --skill verification-loop-cmiller838

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents incomplete or broken work from being marked as done by running a structured multi-phase verification pass over a coding session before a pull request is created. ## Core Features & Use Cases - Six-Phase Verification: Sequentially checks build success, type errors, lint warnings, test results with coverage, security issues like leaked secrets, and the git diff for unintended changes. - Standardized Report: Produces a PASS/FAIL verification report summarizing each phase and an overall READY/NOT READY verdict for the PR. - Use Case: After finishing a feature in a TypeScript project, run the verification loop 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 Verify my current session's work and produce a verification report before I open a pull request.

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 checking, linting, tests with coverage, security scanning, and git diff review. Each phase reports PASS or FAIL, and the final report gives an overall READY or NOT READY verdict for the PR.

What checks should run after finishing a feature in TypeScript?▼

Run npm run build, npx tsc --noEmit for type errors, npm run lint, and the test suite with coverage targeting 80% minimum. Then grep for leaked secrets like API keys and review the git diff for unintended changes.

Does this verification workflow support Python projects?▼

Yes, it includes Python-specific commands: pyright for type checking and ruff check for linting. The build, test, security scan, and diff review phases apply regardless of language.

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

Grep the codebase for patterns like sk- and api_key across source files before committing. The security scan phase also flags leftover console.log statements in TypeScript source directories.

When should verification run during a long coding session?▼

Run verification every 15 minutes or after major changes such as completing a function, finishing a component, or before moving to the next task. Frequent checkpoints catch failures earlier than a single end-of-session review.

Related Skills

Explore More Software Engineering Skills→
Hunt-Gather-CreateHunt-Gather-Create

atomic-commits

Divide working tree changes into logical atomic commits with clear messages.

Official
Intermediate
taracodlabstaracodlabs
799

github-pr-workflow

Manages the full GitHub pull request lifecycle using the gh CLI.

Official
Intermediate
Michae2xlMichae2xl

verification-loop

Verify Claude Code sessions with build, type, lint, test, security, and diff checks.

Community
Advanced
buildworksaibuildworksai

devops-cicd

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

Community
Advanced