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

Document approval gate for git request variants

Browse Source
This commit is contained in:
anthony.wen
2026-03-30 11:28:16 -04:00
parent 63dd40faab
commit 89f558bd39
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
atvm/AGENTS.md
View File

@@ -62,6 +62,8 @@ This file defines how to operate and maintain the ATVM workspace in `/home/aw/co
- Always show exact planned ATVM commands before execution.
- Never execute setup or automation commands that require approval until the operator explicitly approves them.
- For ATVM run approvals, treat `approve` as run-with-watcher and `approve without watcher` as run-without-watcher.
- Treat git/commit requests as a separate approval gate.
- Follow `/home/aw/code/cds/git-guide.md` for commit-request handling, including the rule that phrases such as `create me a git`, `create a git`, `create a git description`, `make me a git`, `make a git`, `make me a git description`, `create me a git description`, and close variations are prepare-only until the operator explicitly approves the displayed commit command.
- After `cmc-templates.py`, always verify that the generated spec files and the config `specPattern` still include every requested VM before starting `run-sorry-cypress.py`.
- If any requested VM is missing after template generation, stop and report the mismatch instead of launching the runner.
- When the watcher is requested, start the watcher before `run-sorry-cypress.py`.

10
git-guide.md
View File

@@ -24,6 +24,16 @@ This file records repo-specific git workflow preferences for `/home/aw/code/cds`
- 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 all of the following as approval-gated prepare-only requests, not as permission to run `git commit`:
- `create me a git`
- `create a git`
- `create a git description`
- `make me a git`
- `make a git`
- `make me a git description`
- `create me a git description`
- Treat close variations of those phrases with the same intent the same way.
- If the request means "prepare or create git/commit wording or a commit", ask for approval first before running any commit action.
- 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.