ecc-verification-loop

Orchestrate Python project verification phases before pull requests.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/karimatayuta/graph-vector-rag --skill ecc-verification-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecc-verification-loop
Source: https://github.com/karimatayuta/graph-vector-rag/tree/main/.claude/skills/ecc-verification-loop
Command: npx skills add https://github.com/karimatayuta/graph-vector-rag --skill ecc-verification-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive verification workflow for Python projects before PRs, covering syntax/build checks, type checks, linting, tests, security scanning, and diff review.

Core Features & Use Cases

  • Orchestrates six phases (build/syntax, type checks, lint, tests, security scans, diff review) to gate quality before merging.
  • Applicable to CI pipelines or local validation across typical Python repos with src/tests.

Quick Start

Run the verification after completing a feature or before submitting a PR to ensure all checks pass.

Frequently Asked Questions about ecc-verification-loop

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

FAQPage Schema
How do I automate Python project verification before submitting a PR?

Automate Python project verification by orchestrating builds, type checks, linting, tests, security scans, and diff reviews. This Skill gates quality before merging by running deterministic commands and reporting structured results across all six phases.

Can I run end-to-end Python verification locally and in CI pipelines?

End-to-end Python verification works in both CI pipelines and local development environments. It applies to typical Python repositories using src/tests structures, allowing developers to validate changes locally before pushing or gate merges automatically in CI.

What does a comprehensive Python pre-PR verification workflow include?

A comprehensive pre-PR verification workflow includes six phases: build and syntax checks, type checks, linting, tests, security scans, and diff reviews. It executes deterministic commands and provides structured reporting for each phase to gate changes.

How do I run type checks, linting, and security scans together for Python code?

Run type checks, linting, and security scans together through an orchestrated verification loop. This process sequentially executes these checks alongside builds and tests, providing structured phase-by-phase reporting to identify code quality or security issues before merging.

Does the Python verification loop support repositories with src and tests directories?

The verification loop supports typical Python repositories with src/tests directory layouts. It applies automated syntax checks, type validation, test execution, and diff reviews to these standard project structures to gate changes before pull requests.

How are verification results reported when gating Python pull requests?

Verification results are reported through structured phase-by-phase outputs for Build, Types, Lint, Tests, Security, and Diff categories. This clear execution reporting ensures developers can quickly identify which specific check failed during the pull request gating process.