venus/CTF-tool
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[GEMINI] Update Core Mandate 7 to explicitly restrict unsolicited testing

Browse Source
This commit is contained in:
venus
2026-07-18 03:08:45 -05:00
parent 72266489da
commit d58587cc65
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
GEMINI.md
View File

@@ -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 (`# {{{ <name>` and `# }}}`).
6. **Matching Test Files:** Every Python implementation file inside `src/` must have a corresponding test file under the `tests/` directory named `test_<filename>.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.