Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
Security grade of this SKILL.md: SAFE · how we grade
How to install setup-pre-commit
npx skills add mattpocock/skills --skill setup-pre-commit -a claude-code
The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.
What the SKILL.md says
Husky pre-commit hook. lint-staged running Prettier on all staged files. Prettier config (if missing). typecheck and test scripts in the pre-commit hook. Check for package-lock.json (npm), pnpm-lock.yaml (pnpm), yarn.lock (yarn), bun.lockb (bun). Use whichever is present. Default to npm if unclear. Install as devDependencies: This creates .husky/ dir and adds prepare: "husky" to package.json. Write this file (no shebang needed for Husky v9+): Adapt: Replace npm with detected package manager. If repo has no typecheck or test script in package.json, omit those lines and tell the user. Only create if no Prettier config exists. Use these defaults: [ ] .husky/pre-commit exists and is executable. [ ] .lintstagedrc exists. [ ] prepare script in package.json is "husky". [ ] prettier config exists. [ ] Run npx lint-staged to verify it works.
Other skills in mattpocock/skills
ask-mattAsk which skill or flow fits your situation. A router over the skills in this repo.
code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's doc…
codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportuniti…
diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throw…
domain-modelingBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or edi…
git-guardrails-claude-codeSet up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wa…
grill-meA relentless interview to sharpen a plan or design.
grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
grillingGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' tri…
handoffCompact the current conversation into a handoff document for another agent to pick up.
implementImplement a piece of work based on a spec or set of tickets.
implement-specImplement the result of /to-spec and /to-tickets in code.
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
migrate-to-shoehornMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests…
prototypeBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right…
researchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants…
scaffold-exercisesCreate exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold…
setup-matt-pocock-skillsConfigure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before f…
tddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integrat…