Agent skill · software engineering · affaan-m
verification-loop
Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.
Why this skill is useful
Adds a comprehensive set of executable scripts for verification phases that enhance code quality checks and readiness for PRs.
What it needs
Requires npm, pnpm, pyright, ruff installed locally. About 2k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Verification Loop Skill A comprehensive verification system for Claude Code sessions. When to Use Invoke this skill: After completing a feature or significant code change Before creating a PR When you want to ensure quality gates pass After refactoring Verification Phases Phase 1: Build Verification If build fails, STOP and fix before continuing. Phase 2: Type Check Report all type errors. Fix critical ones before continuing. Phase 3: Lint Check Use sed to limit displayed output while consuming the whole stream. This keeps a successful linter from failing on SIGPIPE when pipefail is enabled. Phase 4: Test Suite Report: Total tests: X Passed: X Failed: X Coverage: X% Phase 5: Security Scan Phase 6: Diff Review Review each changed file for: Unintended changes Missing error handling Potential edge cases Target Acceptance When the requested outcome requires deployment or target-environment verification, report target acceptance separately from local checks. Record the environment and installed version when known, the evidence, and the next permitted check or precise access dependency. Passing local checks, review, merge, or release does not establish target acceptance. Report VERIFIED or FAILED for an executed target check, with its evidence. Do not access production or make external changes without authorization. For local-only tasks, mark target acceptance as not applicable. For example: local checks PASS; staging verification NOT PERFORMED (no access); next step: an authorized maintainer runs the staging smoke test. Output Format After running all phases, produce a verification report: Continuous Mode For long sessions, run verification every 15 minutes or after major changes: Integration with Hooks This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive review.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/verification-loop--7fb93e