Configures pre-commit hooks for linting, type checking, formatting, and testing.
SkillScore88Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/20/2026
What it changes
Passed 22 of 25 test cases with the skill, and 4 of 25 without it.
Without skill16%
With skill88%
Checks it passed that the model alone missed
Passes the --all flag to component quality scripts
Uses uv run pre-commit install for registering git hooks
Configures pythonpath pointing to src in the testing options
and 21 more in the full report
18 fixed4 passed either way3 still failing0 broke
Pass-rate lift
+72 pp
Tokens
+31%
Agent turns
0%
Response time
-49%
Model gemini-3.6-flashMeasured 8/20/2026v122 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 18
Prompt
We are initializing a new Python project named 'analytics-service' in the current working directory and need to generate .pre-commit-config.yaml using an automation script. What command should be executed?
What was checked, without and with the skill
Checked
Without skill
With skill
Executes attune_init.py with python language and project name parameters
Missed
Passed
case-19 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md213 linessingle file
Pre-commit Setup Skill
Configure a three-layer pre-commit quality system that
enforces linting, type checking, and testing before every
commit.
When To Use
Setting up a new project with code-quality enforcement
Adding pre-commit hooks to an existing project
Upgrading from basic linting to a full quality system
Setting up monorepo or plugin architecture with
per-component quality checks
Updating pre-commit hook versions
When NOT To Use
Pre-commit hooks already configured and working optimally
Project does not use git version control
Team explicitly avoids pre-commit hooks for workflow reasons
Philosophy: Three-Layer Defense
The system is organised in three layers, each with a
different cost / coverage tradeoff:
Layer 1: Standard hooks: fast global checks
(50-200ms total). Lints and type-checks every staged file.
Layer 2: Component-specific checks: per-component
lint, typecheck, and test (10-30s total). Only the
components touched by the staged files are run.
Layer 3: Validation hooks: project-specific
structure and pattern checks (varies). Catches violations
that generic linters miss.
This layering keeps the fast feedback loop fast while still
catching the slow / project-specific bugs before they land.
Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.