Verification Loop Skill

Automate multi-phase code verification with build, type, lint, test, security, and diff checks.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/AndyHsuTW/everything-llm-workspace --skill verification-loop-skill-andyhsutw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Verification Loop Skill
Source: https://github.com/AndyHsuTW/everything-llm-workspace/tree/main/.agents/skills/verification-loop
Command: npx skills add https://github.com/AndyHsuTW/everything-llm-workspace --skill verification-loop-skill-andyhsutw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of verifying code quality, ensuring that builds, type checks, linting, tests, security scans, and diff reviews are all passed before a pull request is created.

Core Features & Use Cases

  • Comprehensive Checks: Covers build, type, lint, test, security, and diff review stages.
  • Quality Gates: Helps maintain a high standard of code quality in a project.
  • Use Case: After completing a new feature, run this skill to automatically confirm that all tests pass, no new type errors were introduced, and no secrets were accidentally committed.

Quick Start

Run the verification loop skill to check the quality of your current code changes.

Frequently Asked Questions about Verification Loop Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code quality checks before creating a pull request?

You can automate code quality checks before a pull request by executing a multi-phase verification process. This includes running builds, type checking, linting, test execution with coverage, and security scanning to ensure comprehensive code readiness.

How does a pre-PR verification loop handle security scanning and console logs?

A pre-PR verification loop handles security scanning by using grep to detect committed secrets and console logs. This automated diff review prevents accidental exposure of sensitive data and debug code in the final pull request.

Can I run type checking and linting with tsc and ruff in a single CI/CD workflow?

Yes, you can run type checking and linting with tsc, pyright, and ruff in a single workflow. Executing these tools alongside npm or pnpm scripts ensures both TypeScript and Python code meets strict quality gates before integration.

What is the best way to verify code readiness for TypeScript and Python projects?

The best way to verify code readiness for TypeScript and Python projects is an automated verification loop. It sequentially executes tsc and pyright for types, ruff for linting, and test suites with coverage to validate all changes comprehensively.

Does automated diff review catch secrets and console logs before pushing code?

Yes, automated diff review catches secrets and console logs before pushing code. By scanning the git diff with grep, the verification process identifies and flags security vulnerabilities and debugging artifacts before pull request creation.

Why do I need to run build, test, and lint checks before a pull request?

You need to run build, test, and lint checks before a pull request to maintain high code quality standards. This verification prevents type errors, test failures, and security vulnerabilities from entering the main branch.