mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Sonnet 4.6
3f9e3b0179
Permission to use --no-verify is single-use per commit. Generic commit requests MUST NOT qualify. Applied MUST/MUST NOT conventions consistently. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Committing
- You MUST commit only after all required checks pass.
- You MUST NOT commit automatically without explicit confirmation from the user. ALWAYS ask before committing.
make testis run automatically by pre-commit before every commit when staged changes include at least one file that is not.md,.rst, or.txt. You do NOT need to run it manually — the pre-commit hook enforces it.- If the pre-commit hook fails, fix the underlying issue and retry the commit.
- You MUST NOT use
--no-verifyunless the user gives a direct, unambiguous instruction to bypass the hook (e.g. "skip the hook", "bypass pre-commit"). - Generic commit requests — such as "commit the changes", "commit", or any equivalent in any language — MUST NOT qualify. When in doubt, you MUST NOT use
--no-verify. - Permission to use
--no-verifyis valid for ONE commit only. You MUST NOT carry it over to subsequent commits unless the user explicitly grants it again. - For markdown/reStructuredText/text-only changes, pre-commit skips
make testautomatically. You MUST NOT run it manually either.