Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions ai_automation/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,17 +33,17 @@ The high-level workflow looks like this:

7. Once the worker finishes, run a review cycle from the worktree before merging:

- If the worker left changes unstaged, run CodeRabbit against the working tree. If they committed, review the commit directly. **Run CodeRabbit only once per branch.** If you need to make follow-up format-only fixes (e.g., gofmt), skip re-running CodeRabbit; rely on your own review instead. Formally:
- Run an AI code review with the whole repository as context: Claude Code's `/code-review` in the worktree, or Codex. If the worker left changes unstaged, review the working tree. If they committed, review the commits against `origin/main`. **Review once per branch.** If you need to make follow-up format-only fixes (e.g., gofmt), skip another review; rely on your own reading instead. With Codex:

```bash
# unstaged diff
coderabbit review --plain --type uncommitted
codex review --uncommitted

# committed changes versus origin/main
coderabbit review --plain --type committed --base-commit origin/main
codex review --base origin/main
```

Address minor suggestions immediately; if coderabbit flags major rework, spin up another worker with a follow-up task entry.
Address minor findings immediately; if the review calls for major rework, spin up another worker with a follow-up task entry.

- Re-run the required `task` commands locally. Do not merge until the branch is fully green (at minimum: `task go:test`).

Expand Down
2 changes: 1 addition & 1 deletion ai_automation/manager_prompt_template.txt
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Your responsibilities:
3. Monitor worker progress, ensuring they run the required `task` commands and keep branches clean.
4. When a worker finishes:
- Enter the worktree and inspect the diff/commits.
- Run CodeRabbit once (e.g. `coderabbit review --plain --type committed --base-commit origin/main`); do not re-run after format-only follow-ups. Apply small fixes immediately or queue follow-up work if feedback is substantial.
- Run one AI code review with the whole repository as context (Claude Code's `/code-review`, or `codex review --base origin/main`); do not re-run after format-only follow-ups. Apply small fixes immediately or queue follow-up work if feedback is substantial.
- Re-run required `task` commands (`task go:test` at minimum) and only merge when the branch is green.
- Merge from the main checkout, then run `task ci` yourself. No new work starts while CI is failing.
5. Update `ai_automation/duplication_tasks.md` with completion notes or follow-up actions, and remove/cleanup the worktree (`git worktree remove`).
Expand Down