verification-loop

Run build, type checking, linting, tests, and security scans before pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cooldaemon/dotfiles --skill verification-loop-cooldaemon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/cooldaemon/dotfiles/tree/main/.claude/skills/verification-loop
Command: npx skills add https://github.com/cooldaemon/dotfiles --skill verification-loop-cooldaemon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures code quality and readiness before submitting a Pull Request, reducing review cycles and catching errors early.

Core Features & Use Cases

  • Automated Checks: Runs build, type checking, linting, and tests.
  • Security Scanning: Detects secrets and dependency vulnerabilities.
  • Code Review Aid: Facilitates a thorough diff review.
  • Use Case: Before pushing your changes for a new feature, run this skill to confirm everything is working as expected and meets project standards.

Quick Start

Run the verification-loop skill to perform pre-PR checks on the current project.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run pre-PR checks for build, linting, and test coverage?

Pre-PR verification executes build, type checking, linting, and test coverage checks to ensure code quality and project standard adherence before submitting a pull request.

What is included in a pre-Pull Request verification checklist?

A pre-Pull Request verification checklist includes build, type checking, linting, test execution with coverage, security scanning for secrets and vulnerabilities, and code diff review.

Can I scan for security secrets and dependency vulnerabilities before pushing code?

Yes, security scanning for secrets and dependency vulnerabilities is included in the pre-Pull Request verification process to catch security issues before pushing code.

Does the verification process support code diff review for new features?

Yes, the verification process facilitates a thorough code diff review for new features, ensuring changes meet project standards and work correctly before pull request submission.

What's the best way to automate pre-commit checks for code quality and security?

Automating pre-commit checks via a verification loop runs build, linting, tests, and security scanning to catch errors early and reduce pull request review cycles.

Why should I run a verification loop before submitting a pull request?

Running a verification loop before submitting a pull request ensures code quality and readiness, reducing review cycles and catching errors early in the development process.