verification-loop

Automates phased verification of builds, types, linting, tests and security checks, outputting a structured report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and automates a multi-phase verification workflow that validates builds, types, lint, tests, and security checks across code changes.

Core Features & Use Cases

  • End-to-end verification of code changes to ensure builds, type correctness, style adherence, and security checks.
  • Applicable after feature implementation, before PR submission, or after refactors to gate quality.
  • Produces a consolidated verification report with pass/fail status and actionable guidance.

Quick Start

Run the verification workflow after implementing a feature to validate all stages.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
What is end-to-end code verification and when do I need it?

End-to-end code verification validates build, type, lint, tests, and security checks across code changes. You need this automated verification after feature implementation, before PR submission, or after refactors to gate quality.

How do I automate build, lint, and security checks before a PR submission?

You automate build, lint, and security checks by running a phased pipeline that validates type correctness, style adherence, and security scans, producing a consolidated verification report with pass/fail status and actionable guidance.

Can I run CI-CD quality assurance checks across diverse software stacks?

Yes, you can run CI-CD quality assurance checks across diverse software stacks. The automated verification workflow applies to software projects of various stacks to validate builds, types, and security.

What's the best way to consolidate type-check and test results into a single report?

The best way to consolidate type-check and test results is using a coordinated multi-phase verification workflow that outputs a structured report with pass/fail status and actionable guidance for code changes.

Why does my automated verification fail after a code refactor?

Automated verification fails after a code refactor when the phased pipeline detects issues across build, type-check, lint, tests, or security scans, outputting a structured report with actionable guidance to resolve them.