precommit-setup

# 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. ## Module Loading The detailed configuration patterns are in modules; load only the ones you need: - `modules/standard-hooks.md`: Layer 1 patterns for Python, Rust, and TypeScript (load when configuring base ...