verification-loop

Automate build, type, lint, test, and security verification before PR.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mitul-bhatia/Vibes --skill verification-loop-mitul-bhatia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/mitul-bhatia/Vibes/tree/main/.github/skills/verification-loop
Command: npx skills add https://github.com/mitul-bhatia/Vibes --skill verification-loop-mitul-bhatia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates comprehensive verification of code sessions to ensure builds, type correctness, linting, tests, and security checks are all satisfied before creating a PR.

Core Features & Use Cases

  • End-to-end verification workflow: orchestrates build, type check, lint, tests, security scans, and diff review across languages (JavaScript/TypeScript and Python).
  • Quality gates: enforces minimum standards (e.g., 80% test coverage) and surfaces actionable failure reports.
  • Use Case: before merging a feature, run the verification loop to catch regressions and policy violations early.

Quick Start

Run the verification loop on your feature branch to validate all quality gates before PR submission.

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, lint, and test checks before creating a PR?

End-to-end verification before a PR orchestrates build, type-check, lint, test, and security scans into a single workflow. This enforces quality gates and catches regressions or policy violations early across multi-language projects.

What is an end-to-end code verification workflow for CI-style gates?

An end-to-end verification workflow coordinates multiple quality gates—builds, type checks, linting, tests, and security scans—across your codebase. It enforces minimum standards like 80% test coverage and surfaces actionable failure reports before merging.

Can I run automated quality checks across both JavaScript and Python projects?

Automated quality checks can be applied to multi-language projects, specifically JavaScript/TypeScript and Python. The verification process enforces a multi-phase validation workflow that runs appropriate checks for each language environment before PR submission.

What's the best way to enforce minimum test coverage and security scans before merging?

Enforcing minimum test coverage and security scans is best achieved by running an automated verification loop on your feature branch. This applies quality gates, such as an 80% coverage requirement, and surfaces security or policy violations prior to PR creation.

Why run a multi-phase validation workflow on a feature branch?

Running a multi-phase validation workflow on a feature branch catches build failures, type errors, lint issues, and security vulnerabilities locally. This prevents broken code from entering the main branch and provides actionable failure reports for quick fixes.