anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify explicit approval requirement for git commits

Browse Source
This commit is contained in:
anthony.wen
2026-03-27 10:23:03 -04:00
parent 53f9e68fcd
commit 4c0e28cc05
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
git-guide.md
View File

@@ -23,7 +23,10 @@ This file records repo-specific git workflow preferences for `/home/aw/code/cds`
- Do not run `git push` immediately after drafting the message. - Do not run `git push` immediately after drafting the message.
- Wait for explicit user approval before creating the commit or running the push command. - Wait for explicit user approval before creating the commit or running the push command.
- Do not treat a request such as "give me the git commit" or "make the commit" as approval by itself. - Do not treat a request such as "give me the git commit" or "make the commit" as approval by itself.
- Do not treat a request such as "create a git for me", "show me a proposed git commit", "prepare the commit", or any similar commit-related wording as approval by itself.
- Treat every commit-related request as prepare-and-show-only until the user explicitly approves the commit after seeing the proposed message or exact command.
- Only execute `git commit` after the user explicitly approves the displayed commit command. - Only execute `git commit` after the user explicitly approves the displayed commit command.
- If there is any ambiguity about whether the user is asking for preparation versus execution, default to not committing.
- If the user changes the requested commit message or scope after commands are shown, rebuild the proposal and wait for fresh approval. - If the user changes the requested commit message or scope after commands are shown, rebuild the proposal and wait for fresh approval.
- After executing `git commit`, always verify that the commit actually succeeded before reporting success. - After executing `git commit`, always verify that the commit actually succeeded before reporting success.
- Verification must include checking that: - Verification must include checking that: