verification-loop

Automate build, type-check, lint, test, security, and diff validation for Claude Code sessions.

1|Updated Jan 30, 2021
One-click install
npx skills add https://github.com/fideguch/my_dotfiles --skill verification-loop-fideguch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/fideguch/my_dotfiles/tree/main/claude/skills/verification-loop
Command: npx skills add https://github.com/fideguch/my_dotfiles --skill verification-loop-fideguch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end quality verification for Claude Code sessions.

Core Features & Use Cases

  • Build verification to ensure the project compiles across environments.
  • Type checks, linting, and tests to catch defects early.
  • Security scans and diff review to surface regressions before PRs.

Quick Start

Run the verification loop after completing a feature or before creating a PR to validate build, type checks, lint, tests, security, and diffs.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I automate build, type-check, lint, and test verification for Claude Code sessions?

Automate end-to-end quality verification by running a repeatable workflow that validates build, type-check, lint, test, security, and diff requirements for JavaScript, TypeScript, and Python projects in local and CI environments.

What's the best way to run quality checks before creating a pull request?

Run an end-to-end quality verification loop after completing a feature or bug fix to validate build, type checks, linting, tests, security scans, and diff reviews to surface regressions before creating a PR.

Does the automated verification loop work with both JavaScript and Python projects?

The verification loop applies to feature development, bug fixes, and refactoring across JavaScript, TypeScript, and Python projects in both local and CI environments, satisfying build, type-check, lint, and test requirements.

How does security scanning and diff review fit into automated quality checks?

Security scans and diff reviews are integrated into the end-to-end quality verification workflow to surface regressions and security issues early, ensuring code defects are caught before PRs are submitted.

Can I use automated quality verification for both local development and CI pipelines?

The verification loop operates across both local and CI environments, applying repeatable build, type-check, lint, test, and security validation workflows to ensure consistent quality across development stages.

When should I run end-to-end quality verification in my development workflow?

Run the verification loop after completing a feature, bug fix, or refactoring task to validate build, type checks, lint, tests, security, and diffs before submitting changes for review.