agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/git-hooks-no-husky/SKILL.md

git-hooks-no-husky

Skill3 starsChanged 4 days agoMITView on GitHub

Husky process steal without the npm package. Keep core.hooksPath=.githooks (relative) so each worktree runs its own hook. Do not install husky. Trigger: husky, typicode.github.io/husky, hooksPath, worktree hooks, would husky help. Slash: /git-hooks-no-husky.

  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Not affiliated. Do not npm i husky.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git hooks without Husky

Source: typicode.github.io/husky (2026-08-18). Not affiliated. Do not npm i husky.

This repo already has the product: tracked .githooks/pre-commit + scripts/install-git-hooks.sh (T-37 ownership + worktree test gate).

What we steal

HuskyHere
Relative core.hooksPath (.husky/_)Relative .githooks so each worktree runs its hook
prepare auto-installscripts/install-git-hooks.sh + bin/hooks-path-doctor --heal
Tiny hook wrapperExisting .githooks/pre-commit — do not rewrite

What we do not steal

The husky npm package, .husky/, HUSKY=0 as a new env, or lint-staged.

Absolute core.hooksPath pointing at the primary checkout makes every worktree run the dirty shared tree's hook. That is the bug this skill exists to prevent.

Run

node tools/hooks-path-doctor.js --json
node tools/hooks-path-doctor.js --heal
scripts/install-git-hooks.sh

NEVER / ALWAYS

NEVERALWAYS
npm i husky / --add-huskyKeep .githooks
Store an absolute hooksPathRelative .githooks
Edit another agent's .githooks/pre-commit claimDoctor + installer only

Related

  • /high-roi-steal-and-finish · /ci-first-fail

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.