Tighten commit approval workflow

This commit is contained in:
Anthony Wen
2026-07-29 11:35:54 -04:00
parent dbfca7e6eb
commit 556cce9408
3 changed files with 14 additions and 2 deletions
+6
View File
@@ -7,6 +7,11 @@ This document provides workspace-level instructions for AI agents working anywhe
### General Workspace Rules
- Always let the user review the proposed commit scope and commit message first, and wait for explicit approval before creating any local git commit in this workspace.
- Treat commit-related wording such as `commit it`, `make the commit`, `create a git`, `give me a commit`, or close variations as a request to prepare the commit for review, not as approval to run `git add` or `git commit`.
- Before running any local `git add` or `git commit`, show the repo path, current branch, exact files to stage, and exact commit message.
- Only run `git add` or `git commit` after the operator replies with the exact phrase `approve commit` for the displayed scope and message.
- If the proposed scope or message changes after review, show the updated scope/message and require a new `approve commit`.
- Never treat approval to commit as approval to push. Pushing requires a separate explicit request after the commit exists.
- Never commit or push to the nested `galaxy-complete` repo under `/home/aw/code/cds/galaxy-complete` without the user's explicit approval.
- Never assume work in `/home/aw/code/cds` should be pushed to `rnd.cdsi.us.com`.
@@ -70,6 +75,7 @@ When the user explicitly asks to "create a git" or otherwise requests git/commit
4. When generating git commands that need SSH, use the user's one-off method exactly as:
`GIT_SSH_COMMAND='ssh -i ~/.ssh/id_ed25519_anthony -o IdentitiesOnly=yes'`
5. Prefer complete copy-pasteable command sequences that are ready to run from `/root/cdc-e2e-cyp-12.17.4`.
6. The exact `approve commit` handshake above applies only to commits this agent would execute locally; ATVM Cypress machine/vm git requests remain draft-only unless the operator explicitly overrides that rule.
If the user does not specify the ATVM Cypress machine/vm, follow the general workspace rules above and any other git guidance already in this file.