From 67aa62557984a2cbb33307ffc76fb475e2f49300 Mon Sep 17 00:00:00 2001 From: Michael Suchacz <203725896+ibetitsmike@users.noreply.github.com> Date: Mon, 11 May 2026 15:14:28 +0200 Subject: [PATCH] chore: add coder-agents-review skill (#25121) ## Summary - Adds the `coder-agents-review` agent skill that drives PRs through the `coder-agents-review` GitHub app review loop - The skill automates: triggering review, waiting for feedback, fixing issues, validating, and re-requesting until approved ## Test plan - [ ] Verify the skill file is well-formed and the loop instructions are correct - [ ] Test triggering the skill on a PR with `/coder-agents-review` Made with [Cursor](https://cursor.com) --------- Co-authored-by: Cursor --- .agents/skills/coder-agents-review/SKILL.md | 33 +++++++-------------- 1 file changed, 10 insertions(+), 23 deletions(-) diff --git a/.agents/skills/coder-agents-review/SKILL.md b/.agents/skills/coder-agents-review/SKILL.md index e63934544b..22b7ce9b98 100644 --- a/.agents/skills/coder-agents-review/SKILL.md +++ b/.agents/skills/coder-agents-review/SKILL.md @@ -12,8 +12,8 @@ has approved the current work. The loop is: -1. if the PR has no existing `coder-agents-review` review or comment, - post `/coder-agents-review` +1. if the PR has no existing `coder-agents-review` review, comment, or + pending trigger, post `/coder-agents-review` 2. wait for `coder-agents-review` to respond 3. fix actionable issues with the smallest safe diff 4. validate and push @@ -39,8 +39,9 @@ If you stop early, say exactly why. ## Non-negotiable behavior - Inspect the PR before posting anything. -- If the PR has no review or comment from `coder-agents-review`, post a - top-level PR comment with the exact body `/coder-agents-review`. +- If the PR has no review or comment from `coder-agents-review` and no + pending trigger comment, post a top-level PR comment with the exact + body `/coder-agents-review`. - If `coder-agents-review` activity is already present, start from that feedback instead of posting a duplicate trigger immediately. - After every fix push, post `/coder-agents-review` again. @@ -52,22 +53,6 @@ If you stop early, say exactly why. with a short fix summary and report the blocker. - Never create or merge a PR unless the user explicitly asks. -## Disclosure rule - -The trigger comment should stay exactly `/coder-agents-review` so the app -can process it reliably. - -If you need to disclose that Mux is acting on Mike's behalf, use a short -separate comment only when that disclosure is not already present on the -PR and only if adding extra text to the slash-command comment could break -the trigger. - -Use this exact disclosure text: - -```text -> Mux is acting on Mike's behalf. -``` - ## Defaults and config Use repository conventions first. Otherwise use these defaults. @@ -235,14 +220,16 @@ login. Do not treat a substring match as sufficient. ### First request -If the PR has no review or comment from `coder-agents-review`, post the -exact trigger comment: +If the PR has no review or comment from `coder-agents-review`, and no +existing `/coder-agents-review` trigger comment that the app has not yet +responded to, post the exact trigger comment: ```bash gh pr comment "$PR_NUMBER" --body "/coder-agents-review" ``` -If needed, add the disclosure comment right after it. +If a trigger comment already exists but the app has not responded yet, +skip posting and enter the wait loop. ### Existing activity already present