From 4c0e28cc05ad5e247624b57d160ff8f1a9722c1c Mon Sep 17 00:00:00 2001 From: "anthony.wen" Date: Fri, 27 Mar 2026 10:23:03 -0400 Subject: [PATCH] Clarify explicit approval requirement for git commits --- git-guide.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/git-guide.md b/git-guide.md index 77eb020..7f03f67 100644 --- a/git-guide.md +++ b/git-guide.md @@ -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. - 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 "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. +- 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. - After executing `git commit`, always verify that the commit actually succeeded before reporting success. - Verification must include checking that: