skills.rest
KuaaMU
KuaaMUCOMMUNITY
Explore all skills by this author →
𝕏@X_SwarmMindGitHub

verification-loop

Execute multi-phase code verification covering build, type checking, linting, tests, and security scans.

4|Updated Feb 14, 2026
Search Tags:#code quality#testing#linting#verification#security scan#pr check
One-click install
npx skills add https://github.com/KuaaMU/omnihive --skill verification-loop-kuaamu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/KuaaMU/omnihive/tree/main/library/ecc-skills/verification-loop
Command: npx skills add https://github.com/KuaaMU/omnihive --skill verification-loop-kuaamu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of verifying code quality, build status, test coverage, and security before submitting a Pull Request, reducing the likelihood of introducing bugs or vulnerabilities.

Core Features & Use Cases

  • Multi-Phase Verification: Runs through build, type checking, linting, testing, security scans, and diff reviews.
  • Quality Gates: Helps ensure that code meets predefined quality standards.
  • Use Case: Before merging a new feature, run this skill to automatically catch any build errors, type mismatches, failing tests, or potential security issues, providing a clear report on readiness.

Quick Start

Run the verification loop to check the current state of the project.

Frequently Asked Questions about verification-loop

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

FAQPage Schema
How do I check code quality and test coverage before submitting a pull request?▼

To check code quality before a PR, you need an automated verification process that runs builds, type checking, linting, tests, and security scans. This provides a structured report indicating your code's readiness for submission.

What is included in an automated code verification loop for pull requests?▼

An automated code verification loop for pull requests includes multi-phase checks: building, type checking, linting, executing the test suite with coverage, scanning for security secrets, and reviewing the final diff.

How do I scan my codebase for security secrets and logs before merging?▼

You can scan for security secrets and logs before merging by running a security scan phase within a comprehensive verification loop. This catches potential vulnerabilities and provides a clear report on code readiness.

Does a pre-PR code verification process check for type mismatches and build errors?▼

Yes, a pre-PR code verification process explicitly checks for build errors and type mismatches. It runs through dedicated build and type checking phases to ensure code meets predefined quality standards.

Can I use automated quality gates to catch failing tests before a PR?▼

Yes, you can use automated quality gates to catch failing tests before a PR. By executing the test suite with coverage during the verification loop, you ensure your feature meets quality standards and prevents introducing bugs.

Related Skills

Explore More Software Engineering Skills→
adamayoungadamayoung
1

fix-pr-checks

Diagnose and fix failing GitHub pull request status checks.

Community
Advanced
kamp-uskamp-us
25

ship-it

Automate squash merging of verified Pull Requests with green CI status.

Official
Advanced
AsiaOstrichAsiaOstrich
70

checkin

Verify build status, tests, code quality, and workflow compliance before committing.

Community
Intermediate
FFCfelps1FFCfelps1

ce-test-xcode

Automate iOS app build and test processes on simulators via XcodeBuildMCP.

Community
Advanced