Run hooks manually

Run hooks manually in Git — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need to run the repository hooks on demand from my machine. Execute the pre-commit and pre-push…
I need to run the repository hooks on demand from my machine. Execute the pre-commit and pre-push hook scripts manually against the current staged changes on branch bugfix/timeout. Share the exact commands you ran and the output so I can paste them into an onboarding doc. Ladder":"L1"

Improve — make it easier to accept

+
Before I include manual run instructions for other engineers, make them easy and robust. Put the…
Before I include manual run instructions for other engineers, make them easy and robust. Put the simplest command to run both hooks in one line, add a note about required environment variables and Node/Python versions, and flag common failure messages with the suggested fix. Highlight how to run the hooks on Windows vs macOS. Ladder":"L2"

Decide — diagnose the stuck moment

+
I manually executed the pre-commit script against staged files and it returned exit code 1 with a…

I ran the hook script and it exited with a nonzero code

I manually executed the pre-commit script against staged files and it returned exit code 1 with a terse error about linting. I worry the lint config differs from CI and I cannot tell whether to change local config or adjust CI. What is the most likely mismatch and the best next command to confirm where the failure originates? Ladder":"L5"

Become — change the pattern

+
Every sprint several engineers waste an hour trying to reproduce hook failures locally because…

Developers repeatedly ask how to run hooks manually

Every sprint several engineers waste an hour trying to reproduce hook failures locally because instructions are scattered and environment parity with CI is poor. Where should we standardize one simple practice so manual runs stop being a blocker, and what single documentation snippet should live in the repo root to fix this? Ladder":"L6"

Next to this one

Other version control work people do in Git.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.