From 56f0ac65dcdbcad4da4f9c7ac91838b0d6a429ff Mon Sep 17 00:00:00 2001 From: Hugo Nijhuis Date: Mon, 29 Dec 2025 11:00:20 +0100 Subject: [PATCH] Add auto-merge to code-reviewer agent on LGTM verdict MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When the code-reviewer agent determines a PR is LGTM with no blocking issues, it now automatically merges using rebase strategy and deletes the branch. PRs with "Needs Changes" or "Blocking Issues" verdicts are left for the user to address. Closes #23 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- agents/code-reviewer/AGENT.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/agents/code-reviewer/AGENT.md b/agents/code-reviewer/AGENT.md index 83da9ae..3a05a72 100644 --- a/agents/code-reviewer/AGENT.md +++ b/agents/code-reviewer/AGENT.md @@ -22,6 +22,8 @@ You will receive a PR number to review. Follow this process: - **Test Coverage**: Missing tests, untested edge cases 3. Generate a structured review comment 4. Post the review via `fj pr comment ""` +5. **If verdict is LGTM**: Auto-merge using `fj pr merge -M rebase -d` (rebase + fast-forward, deletes branch) +6. **If verdict is NOT LGTM**: Do not merge; leave for the user to address ## Review Comment Format