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.
npx skills add opensquilla/opensquilla --skill meta-pre-commit-quality-gate --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`.
- Trigger surface
- Fallback
What does the meta-pre-commit-quality-gate skill do?
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.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill meta-pre-commit-quality-gate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.