Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evgeniiperov/setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo.
Passed 2 of 11 test cases with the skill, and 9 of 11 without it.
1 fixed3 passed either way13 still failing6 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I want pre-commit checks that format files, check TypeScript types, and run tests. In what sequence should these tasks be configured inside the pre-commit hook file?
| Checked | Without skill | With skill |
|---|---|---|
| Places the staged file formatting step at the top of .husky/pre-commit | Missed | Passed |
| Places typecheck before test in the execution order inside .husky/pre-commit | 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 9 / 11 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.