verification-loop

Automate end-to-end code verification across build, type check, lint, tests, and diff review.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill verification-loop-jamkris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/verification-loop
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill verification-loop-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification of code changes across build, type-check, lint, tests, and security checks to ensure quality gates before PRs.

Core Features & Use Cases

  • End-to-end verification phases: Build, Type Check, Lint, Tests, Security, and Diff Review to gate PR readiness.
  • Standardized reporting: Consistent per-phase status and a final verification report for audits.
  • Real-world use case: Before opening a PR, run the loop to catch regressions across languages and tools.

Quick Start

Run the verification loop to execute all phases and generate a PR-ready report.

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 tests before opening a PR?

Automating build, type check, lint, and tests before a PR involves running an end-to-end verification loop across these phases. This enforces quality gates and generates a standardized report to confirm code readiness.

Can I run a verification loop across mixed TypeScript and Python projects?

Yes, you can run a verification loop across mixed TypeScript, Python, and JavaScript ecosystems. It applies standardized phase steps and reporting across these languages to gate PR readiness in mixed environments.

What is the best way to enforce quality gates in Gemini CLI workflows?

Enforcing quality gates in Gemini CLI workflows is best achieved by automating an end-to-end verification loop. It handles Build, Type Check, Lint, Tests, Security, and Diff Review phases to produce a final verification report.

How does automated diff review work for code changes before a pull request?

Automated diff review works by executing a structured verification plan across code changes. It evaluates the diff alongside build, lint, and test results to gate PR readiness and generate a standardized audit report.

Does the verification loop support reproducible CI steps for code changes?

Yes, the verification loop supports reproducible CI steps by applying standardized reporting and a structured verification plan. It executes phase steps consistently across build, type check, lint, and tests to ensure reproducible results.