You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/AGENTS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ State lives in the master issue body as a hidden HTML comment:
86
86
### Phases
87
87
88
88
-**DEV**: Initial agent run. Agent creates a PR. Transition to `REVIEW`.
89
-
-**REVIEW**: Agent reviews the PR. If approved and no `auto-merge` label, transition to `HUMAN_REVIEW`. If `auto-merge`, transition to `MERGE`. If changes requested, transition to `FEEDBACK`.
89
+
-**REVIEW**: Agent reviews the PR. The orchestrator posts `/oc review` with explicit instructions requiring the final line to be exactly `Verdict: approve` or `Verdict: request-changes`. If approved and no `auto-merge` label, transition to `HUMAN_REVIEW`. If `auto-merge`, transition to `MERGE`. If changes requested, transition to `FEEDBACK`.
90
90
-**FEEDBACK**: Agent addresses review comments. Transition to `REVIEW`.
91
91
-**HUMAN_REVIEW**: Orchestrator waits for native GitHub PR review from a human maintainer. Approval → `MERGE`, Request changes → `FEEDBACK`.
92
92
-**MERGE**: Orchestrator squashes the PR and deletes the branch inline.
return'/oc review\n\nYou are reviewing a pull request for the orchestrator. Your final line must be exactly one of:\nVerdict: approve\nVerdict: request-changes\n\nUse "Verdict: request-changes" if the PR needs code changes. Use "Verdict: approve" only if the PR is correct and ready for the next orchestrator phase.';
0 commit comments