← ClaudeAtlas

setup-git-hookslisted

Configure two-stage git hooks (pre-commit + pre-push) for quality automation, with either pre-commit or lefthook as the hook manager. Use after bootstrap-project and setup-adrs, when adding quality gates to an existing project, or when standardizing quality automation.
jrjsmrtn/project-orchestration-skills · ★ 15 · Code & Development · score 81
Install: claude install-skill jrjsmrtn/project-orchestration-skills
# Setup Git Hooks Configure two-stage git hooks — fast checks on commit, thorough checks on push — using either `pre-commit` or `lefthook` as the hook manager. ## When to Use - After running `bootstrap-project` and `setup-adrs` skills - When adding quality gates to an existing project - When standardizing quality automation across projects ## Required Inputs 1. **Technology stack** (Elixir, Python, TypeScript, etc.) 2. **Quality tools preference** (can use defaults for each ecosystem) 3. **Multi-remote strategy** (if using private + public remotes) ## Two-Stage Strategy **Stage 1: Pre-commit (Fast, <30 seconds)** - File hygiene (whitespace, line endings, merge conflicts) - Secret detection (critical security gate) - Code formatting check **Stage 2: Pre-push (Thorough, <3 minutes)** - Linting with strict rules - Type checking - Security audit (dependencies) - Fast tests (exclude slow/integration) ## Workflow ### Step 0: Create Quality Configuration Reference Before configuring tools, create the single source of truth: `docs/reference/quality-configuration.md` ```markdown # Quality Configuration Single source of truth for all quality settings. ## Toolchain Versions Three roles, and conflating them ships defects. Record all three even when two coincide today. | Role | Version | Declared in | Meaning | |------|---------|-------------|---------| | **Floor** | [oldest supported] | [manifest] | the oldest a *consumer* needs — a compatibility claim | | **Build** | [cu