3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+I need the repository to enforce commit message and pre-push checks. Install the server-side and…
Execute — do the immediate task
+I need the repository to enforce commit message and pre-push checks. Install the server-side and client-side hook scripts in our project root, make them executable, and register the pre-commit and pre-push hooks so developers get blocked locally. Do one test commit on my feature branch feature/payment-retries and confirm the pre-commit rejects a message missing the ticket number. Ladder":"L1"
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I add these hooks across the team, make the failure modes obvious to reviewers. Surface the…
Improve — make it easier to accept
+Before I add these hooks across the team, make the failure modes obvious to reviewers. Surface the ticket-number requirement at the top of the pre-commit output, show a short example of an acceptable commit message, and make the pre-push hook print the exact command to bypass for CI only. Flag anything that would surprise a developer who has a different shell or Windows. Ladder":"L2"
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep wasting time troubleshooting why local hooks don't run for new engineers and why CI…
Become — change the pattern
+Hooks fail to reach all developers reliably
We keep wasting time troubleshooting why local hooks don't run for new engineers and why CI sometimes lets bad commits through. Over the last six months the recurring pattern is manual copying, platform differences, and missing documentation. Recommend one habit and one small repository change that will make hook installation automatic and reliable for all developers joining the team. Ladder":"L6"
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
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.