verification-loop

Run build, type, lint, test, security, and diff checks to produce a release-readiness report.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill verification-loop-mostafa-ismail-2004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/verification-loop
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill verification-loop-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify that a change is actually ready to ship by checking build health, types, lint, tests, security signals, and the final diff in one disciplined pass.

Core Features & Use Cases

  • Build and type validation: Confirms the project compiles and static types are clean before you move on.
  • Quality and safety checks: Runs linting, test coverage review, and basic secret or debug-log scans to surface regressions and risky changes.
  • Use Case: After finishing a feature or refactor, use this Skill to produce a PR-ready verification report with clear pass/fail status and prioritized fixes.

Quick Start

Use the verification-loop skill to run the full verification workflow on my latest changes and return a PR-readiness report.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I run a full release readiness check before creating a pull request?

Run a full release readiness check by validating build health, types, lint, tests, security scans, and diff review in one pass. This produces a PR-readiness report with clear pass/fail status and prioritized fixes.

What is included in a code verification loop for feature handoff?

A code verification loop includes build and type validation, linting, test coverage review, basic secret scans, debug-log scans, and change inspection. These checks surface regressions and risky changes before handoff.

How do I catch security issues and debug logs before refactoring code?

Catch security issues and debug logs by running static analysis and secret scans during the verification workflow. This surfaces risky changes and debug-log leaks before finalizing a refactor.

Can I use automated code review to generate a PR-readiness report?

Automated code review generates a PR-readiness report by applying structured verification across build, lint, test, and diff inspection steps. It requires build commands, static analysis, and test execution to produce consistent results.

What do I need to run type checking and linting for a final quality gate?

Running type checking and linting for a final quality gate requires build commands, static analysis tools, and test execution. These inputs produce a consistent readiness report with actionable fixes.

When should I not use a full verification workflow for my code changes?

Avoid a full verification workflow for trivial changes that do not require build validation, static analysis, or test execution. The workflow is designed for structured quality gates before pull requests, refactors, or feature handoffs.