meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
69
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Pre-Commit Quality Gate (Meta-Skill)
A combinator-style meta-skill that runs three independent quality gates in parallel over the currently-staged diff, then arbitrates a single ship-readiness verdict.
Trigger surface
Fire by saying pre-commit quality gate or one of the localized triggers
listed in the frontmatter. The skill is also designed to be invoked from a git
pre-commit hook via the soft path (meta_invoke), but hook installation is a
separate manual step.
Fallback
If the orchestrator fails (sub-Agent error, timeout, etc.), the
caller should manually run, in order: uv run ruff check src tests,
uv run mypy src/opensquilla --show-error-codes, then
uv run pytest -q. The same three commands are the CI quality gate
in .github/workflows/ci.yml.
- Repository
- TokenRhythm/opensquilla
- Commit
94ac35e
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.