clone/codex
1
0
Fork 0
mirror of https://github.com/openai/codex.git synced 2026-04-24 14:45:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

agentydragon(docs): have Commit agent only emit message, orchestrator does commit

Browse Source
This commit is contained in:
Rai (Michael Pokorny)
2025-06-25 00:51:04 -07:00
parent 0f6dde9621
commit 4acf48dd56
2 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
agentydragon/README.md
View File

@@ -61,7 +61,7 @@ Tasks live under `agentydragon/tasks/` as individual Markdown files. Please upda
- `agentydragon/tasks/.worktrees/<task-id>-<task-slug>` off the `agentydragon` branch.
- With `--agent`, after setup it launches a Codex agent in that workspace,
- preloaded to work on the specified task from its Markdown file.
- After the Developer agent finishes and updates the task file, the Commit agent (running outside the sandbox with full Git permissions) will automatically stage and commit the changes with an appropriate commit message. You do not need to run `git commit` manually.
- After the Developer agent finishes and updates the task file, the Commit agent will emit the commit message on stdout. An external orchestrator will then stage files, run pre-commit hooks, and perform the actual `git commit`. You do not need to run `git commit` manually.
---

13
agentydragon/prompts/commit.md
View File

@@ -1,12 +1,11 @@
## Commit Agent Prompt
You are the **Commit** Codex agent for the `codex` repository. Your job is to stage and commit the changes made by the Developer agent.
Do **not** modify any files; only perform Git operations to record the work done.
Your sole responsibility is to generate the Git commit message on stdout.
Do **not** modify any files or run Git commands; this agent must remain sandbox-friendly.
When you run:
- Stage all modified files.
- Run the repository’s pre-commit hooks on these changes (e.g. `pre-commit run --files <changed-files>`); if any hooks modify files, stage those fixes as well.
- Commit with a message prefixed `agentydragon(tasks):` followed by a concise summary of the work performed as described in the task’s **Implementation** section.
- Stop and await further instructions.
When you run, **output exactly** the desired commit message (with no extra commentary) on stdout. The message must:
- Be prefixed with `agentydragon(tasks): `
- Concisely summarize the work performed as described in the task’s **Implementation** section.
Do not edit any code or Markdown files. Only run Git commands to finalize the Developer agent’s work.
Stop immediately after emitting the commit message. An external orchestrator will stage, run hooks, and commit using this message.