From d58587cc65430017eea4b9de0fadbc0b292c05cd Mon Sep 17 00:00:00 2001 From: venus Date: Sat, 18 Jul 2026 03:08:45 -0500 Subject: [PATCH] [GEMINI] Update Core Mandate 7 to explicitly restrict unsolicited testing --- GEMINI.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/GEMINI.md b/GEMINI.md index 1d5f020..aeff77a 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -12,7 +12,7 @@ The primary goal is to use the context of CTF challenges (forensics, crypto, web 4. **Educational Context:** Use the existing scripts and tools in this repository (like `psk_crack.py`, `exploit.sh`, or the `tools/` directory) as examples when explaining technical concepts. 5. **Vim Folding Markers:** Wrap all classes, command groups, subcommands, and functions inside project implementation files in standard Vim/Neovim folding syntax markers (`# {{{ ` and `# }}}`). 6. **Matching Test Files:** Every Python implementation file inside `src/` must have a corresponding test file under the `tests/` directory named `test_.py`. -7. **Write Only, Do Not Run**: The agent must only write code and tests. Do not attempt to run tests or execute command-line scripts; the user will handle all execution, verification, and testing tasks. +7. **Write Only, Do Not Run**: The agent must only write code and tests. Do not attempt to run tests, execute command-line scripts, or execute commands (like pytest) unless the user explicitly asks for execution in their prompt; the user will handle all execution, verification, and testing tasks. ## Interaction Workflow When discussing new implementations, features, or additions: @@ -20,7 +20,7 @@ When discussing new implementations, features, or additions: 2. **The Pitch**: Provide a clear, technical pitch detailing the planned code modifications. 3. **Implementation Cycle**: Once the user approves the pitch: * **Add Test Cases**: Write or update the corresponding test cases in the test files (e.g. `tests/test_forensics.py`) following the SDET instructions. - * **Git Commit Current State**: Create a git commit of the current workspace state (including the new tests) *before* modifying any implementation files. + * **Git Commit Current State**: Create a git commit of the current workspace state (including the new tests) *before* modifying any implementation files. The commit message MUST start with `[GEMINI]` as the author prefix (e.g., `git commit -m "[GEMINI] Write tests for forensics"`). * **Update the Codebase**: Write/update the actual project implementation files as approved. Do **NOT** create a git commit after writing this implementation code. This ensures all implementation changes remain unstaged so the user can easily run `git diff` to review them. * **Hand Over**: Present the changes to the user so they can run the tests. Do not run the tests yourself.