verification-loop

Name: verification-loop
Availability: InStock
Author: unju-ai

Automate build, type, lint, test, security, and diff verification phases.

Updated Mar 2, 2026

Search Tags:#code quality #testing #linting #CI/CD #verification #security scan

Ready to run

npx skills add https://github.com/unju-ai/ecc --skill verification-loop-unju-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/unju-ai/ecc/tree/main/.agents/skills/verification-loop
Command: npx skills add https://github.com/unju-ai/ecc --skill verification-loop-unju-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the crucial quality assurance steps for code, ensuring that projects are built, typed, linted, tested, and reviewed for security before being considered ready for integration or deployment.

Core Features & Use Cases

Comprehensive Checks: Executes build, type, lint, test, and security scans.
Quality Gates: Provides clear PASS/FAIL status for each verification phase.
Use Case: Before submitting a pull request for a new feature, run this skill to catch any build errors, type mismatches, linting issues, failing tests, or potential security vulnerabilities, ensuring a cleaner and more stable codebase.

Quick Start

Run the verification loop skill to check the current codebase.

Frequently Asked Questions about verification-loop

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

FAQPage Schema

How do I automate code quality checks before deployment?▼

Automating code quality checks before deployment requires running a multi-phase verification process that includes building, type checking, linting, test execution with coverage, and security scanning to ensure code integrity and readiness for integration.

What is a deterministic quality gate for pre-commit checks?▼

A deterministic quality gate for pre-commit checks is an automated verification standard that provides clear PASS or FAIL status for build, type, lint, test, and security scan phases to ensure codebase stability before integration.

How do I run linting, type checking, and security scans in one workflow?▼

To run linting, type checking, and security scans in one workflow, execute an automated verification loop that sequentially processes build validation, linting rules, test coverage execution, and vulnerability detection to review code diffs comprehensively.

Does automated code verification work for pull request integration?▼

Automated code verification works for pull request integration by catching build errors, type mismatches, linting issues, failing tests, and security vulnerabilities before submission, ensuring a cleaner and more stable codebase for downstream merging.

What is the best way to catch security vulnerabilities and linting issues before a pull request?▼

The best way to catch security vulnerabilities and linting issues before a pull request is running a comprehensive code verification loop that executes security scanning and linting phases, returning a clear PASS or FAIL status for each quality gate.