verification-loop

Automate build, type checking, linting, tests, security scans, and diff review.

1|Updated Mar 4, 2026

Search Tags:#code quality #testing #linting #CI/CD #verification #security scan

Ready to run

npx skills add https://github.com/flatrick/mdt --skill verification-loop-flatrick

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/flatrick/mdt/tree/main/skills/verification-loop
Command: npx skills add https://github.com/flatrick/mdt --skill verification-loop-flatrick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of verifying code quality, build stability, and adherence to standards, ensuring that code is ready for review and deployment.

Core Features & Use Cases

Multi-Phase Verification: Executes a series of checks including build, type checking, linting, testing, security scanning, and diff review.
Quality Gates: Acts as a crucial step before submitting code for review or merging.
Use Case: Before submitting a pull request for a new feature, run this skill to catch any build errors, type mismatches, linting issues, failing tests, or potential security vulnerabilities, ensuring a smoother review process.

Quick Start

Run the verification-loop skill to check the current codebase for quality and readiness.

Frequently Asked Questions about verification-loop

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

FAQPage Schema

How do I automate code verification before submitting a pull request?▼

Automating code verification before a pull request requires running multi-phase checks including build, type checking, linting, testing, and security scanning to ensure code quality. This process catches build errors, type mismatches, and failing tests early for a smoother review.

What is included in a comprehensive code quality and readiness check?▼

A comprehensive code quality and readiness check includes build verification, type checking, linting, test execution with coverage, security scanning for secrets and console logs, and diff review. These phases identify and report issues across critical areas before deployment.

How can I run security scans for secrets and console logs in my codebase?▼

Security scanning for secrets and console logs is executed as an automated phase within a multi-step verification loop. It identifies potential vulnerabilities and logging artifacts by analyzing the codebase diff before code review.

Does the verification process check test execution and coverage?▼

Yes, test execution with coverage is a core phase of the verification process. It runs your tests to verify code stability and reports coverage metrics to ensure adherence to quality standards.

What's the best way to catch linting issues and type mismatches before merging?▼

The best way to catch linting issues and type mismatches before merging is to run an automated verification loop. It systematically checks types and lints the codebase, reporting errors to fix prior to pull request submission.

Can I review code diffs for errors as part of my CI/CD pipeline?▼

Diff review is integrated into the automated verification pipeline to catch errors as part of CI/CD workflows. It reviews code changes alongside build and test checks to ensure readiness for pull requests.