Individual skill
git-hook-automation-designer
Configures pre-commit and pre-push hooks (Husky, Lefthook) for fast lint-staged, branch naming, and secret blocking.
skills/utilities/git-hook-automation-designer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 585 bytesSKILL.mdcore · 1,793 bytesexamples/example.mddoc · 707 bytes
Read excerpt
## Purpose
Design fast, unobtrusive client-side Git hooks using Husky, Lefthook, or pre-commit to automatically run lint-staged formatting, branch naming enforcement, secret detection, and commit message linting before code leaves the developer's machine.
## When to Use
- Preventing broken code, unformatted files, and accidental secret keys from being pushed to GitHub.
- Standardizing Conventional Commits across team members (`commitlint`).
- Accelerating local feedback so CI doesn't fail on trivial formatting mistakes.
## What to Analyze
1. **Hook Framework Selection**: Lefthook (super-fast parallel execution in Go/binary) vs Husky + lint-staged (standard Node ecosystem).
2. **Pre-Commit Scope**: Run linters and formatters strictly on *staged* files (`lint-staged`) to keep hook execution under 2 seconds.