Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mattpocock/setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo.
Passed 17 of 20 test cases with the skill, and 15 of 20 without it.
and 1 more in the full report
3 fixed16 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
After creating and staging all pre-commit configuration files, what exact git commit message should be used for the setup commit?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies commit message Add pre-commit hooks (husky + lint-staged + prettier). | Missed | Passed |
The instructions your model reads when the skill loads.
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:
husky lint-staged prettier
npx husky init
This creates .husky/ dir and adds prepare: "husky" to package.json.
.husky/pre-commitWrite this file (no shebang needed for Husky v9+):
npx lint-staged
npm run typecheck
npm run test
test cases passed, vs 15 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.