meta-pre-commit-quality-gate

Name: meta-pre-commit-quality-gate
Availability: InStock
Author: opensquilla

Runs ruff, mypy, and pytest in parallel over staged diffs and arbitrates a BLOCK or APPROVE verdict.

6.8k|540|Updated May 6, 2026

Search Tags:#quality gate #pre-commit #mypy #Ruff #ci #PyTest #Code quality

Ready to run

npx skills add https://github.com/opensquilla/opensquilla --skill meta-pre-commit-quality-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meta-pre-commit-quality-gate
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/exp/meta-pre-commit-quality-gate
Command: npx skills add https://github.com/opensquilla/opensquilla --skill meta-pre-commit-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Committing code without running the full quality gate set leads to CI failures discovered only after push. This Skill runs the exact same three gates that CI enforces (ruff linting, mypy type checking, and pytest) against your staged changes before you commit, then returns a single ship-readiness verdict.

Core Features & Use Cases

Parallel Quality Gates: Executes ruff, mypy, and pytest concurrently over the staged diff via sub-agents, rather than running them sequentially by hand.
Strict Verdict Arbitration: Aggregates the three gate results into one BLOCK or APPROVE decision, where any single failure blocks the commit.
Persistent Audit Trail: Appends each invocation's staged files, gate outputs, and verdict to a memory file for later review.
Use Case: Before committing a refactor touching several Python modules, invoke the gate to confirm lint, types, and affected tests all pass locally, matching what CI will check.

Quick Start

Ask the agent to run the pre-commit quality gate on your currently staged changes before committing.

Frequently Asked Questions about meta-pre-commit-quality-gate

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

FAQPage Schema

How do I run ruff, mypy, and pytest before committing?▼

Invoke the pre-commit quality gate trigger phrase with your changes staged. The skill collects staged files via git diff, runs all three tools in parallel through sub-agents, and returns one BLOCK or APPROVE verdict.

What checks does a pre-commit quality gate run on Python code?▼

This gate runs three checks: ruff for lint violations on staged .py files, mypy with error codes for staged files under src/opensquilla/, and pytest on test files affected by the staged changes.

Does the quality gate work when no Python files are staged?▼

Yes. If the staged list is empty or contains no .py files, ruff is treated as PASS. Similarly, mypy passes when no files under src/opensquilla/ are staged, so the verdict reflects only relevant gates.

What happens if the pre-commit gate orchestration fails?▼

If a sub-agent errors or times out, run the fallback commands manually in order: uv run ruff check src tests, uv run mypy src/opensquilla --show-error-codes, then uv run pytest -q. These match the CI workflow.

Can one failing check still allow the commit to pass?▼

No. The arbitration rule is strict: if any of the three gates reports FAIL, the final verdict is BLOCK with each failing gate's output listed. APPROVE requires all three to report PASS.