agentleFS
intelligentcode-aiintelligentcode-ai/skills/skills/pr-automerge/SKILL.md

pr-automerge

Skill1 starsChanged 9 months agoMITView on GitHub

Activate when asked to auto-review and merge a PR. Runs a closed-loop workflow: subagent Stage 3 review -> fix findings -> re-review -> post ICA-REVIEW receipt -> merge (optional via workflow.auto_merge).

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Default base branch for PRs is dev.

    line 29
  2. Very specific:

    Never merge unless a merge-eligible ICA-REVIEW-RECEIPT exists for the PR's current head SHA:

    line 30
  3. Very specific:

    If workflow.auto_merge=true (standing approval), the agent MAY merge once gates pass.

    line 39
  4. Distinctive:

    Run Stage 3 review via a dedicated reviewer subagent:

    line 47
  5. Distinctive:

    Use your Task/sub-agent mechanism to run Reviewer Stage 3 in a temp checkout.

    line 48
  6. Very specific:

    If PR author == current authenticated gh user: GitHub forbids approving your own PR (server-side rule).

    line 56
  7. Distinctive:

    If repo rules require approvals, merge will still be blocked.

    line 57
  8. Distinctive:

    Verify merge gates (receipt + head SHA + checks green).

    line 58
  9. Distinctive:

    If repeated failures or unclear/risky changes are required, pause for a human decision.

    line 61
  10. Very specific:

    If workflow.auto_merge=true and base is dev: merge the PR (agent-performed merge.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PR Auto-Review And Merge (Closed Loop)

This skill implements the closed-loop workflow: Review via subagent -> ICA-REVIEW receipt -> merge when NO FINDINGS -> otherwise fix and restart.

Inputs

  • PR number (required): <PR-number>

Safety Rules

  • Default base branch for PRs is dev. Never auto-merge a PR targeting main unless it is an explicitly requested release workflow.
  • Never merge unless a merge-eligible ICA-REVIEW-RECEIPT exists for the PR's current head SHA:
    • Reviewer-Stage: 3 (temp checkout)
    • Reviewer-Agent: ... (subagent)
    • Head-SHA matches headRefOid
    • Findings: 0 and NO FINDINGS
    • Result: PASS
  • GitHub approvals are OPTIONAL by default (self-review-and-merge workflow). If you want to enforce GitHub-style approvals, set workflow.require_github_approval=true.
  • Merge approval:
    • If workflow.auto_merge=true (standing approval), the agent MAY merge once gates pass.
    • Otherwise, stop and wait for explicit user approval.

Workflow (Loop Until Clean)

  1. Read PR metadata:
    • base branch, head SHA, head branch
    • checks status
  2. Run Stage 3 review via a dedicated reviewer subagent:
    • Use your Task/sub-agent mechanism to run Reviewer Stage 3 in a temp checkout.
    • Reviewer must fix findings by pushing commits to the PR branch.
    • Reviewer must re-run Stage 3 until findings are zero and checks are green.
    • Reviewer must post ICA-REVIEW-RECEIPT NO FINDINGS comment for the current head SHA.
    • Pragmatic GitHub approval (best-effort; only if workflow.require_github_approval=true): after posting NO FINDINGS receipt, reviewer subagent should:
      • Skip if an APPROVED review already exists.
      • Otherwise, attempt: gh pr review <PR-number> --approve --body "Approved based on ICA Stage 3 review receipt (NO FINDINGS)."
      • If PR author == current authenticated gh user: GitHub forbids approving your own PR (server-side rule). Skip.
        • If repo rules require approvals, merge will still be blocked; use a second GitHub identity/bot for approvals.
  3. Verify merge gates (receipt + head SHA + checks green).
  4. If gates fail:
    • Restart from step 2 (fresh temp checkout).
    • If repeated failures or unclear/risky changes are required, pause for a human decision.
  5. If gates pass:
    • If workflow.auto_merge=true and base is dev: merge the PR (agent-performed merge; do NOT use --auto).
    • Else: stop and ask for explicit approval.

Command Snippets (Reference)

PR info:

PR=<PR-number>
gh pr view "$PR" --json number,baseRefName,headRefName,headRefOid,state,mergeable --jq .
gh pr checks "$PR"

Approval check (optional gate):

PR=<PR-number>
PR_AUTHOR=$(gh pr view "$PR" --json author --jq .author.login)
GH_USER=$(gh api user --jq .login)
APPROVALS=$(gh pr view "$PR" --json reviews --jq '[.reviews[] | select(.state=="APPROVED")] | length')
echo "Approvals: $APPROVALS"
if [ "$PR_AUTHOR" = "$GH_USER" ]; then
  echo "Self-authored PR ($GH_USER): GitHub forbids self-approval; approvals may require a bot/second identity."
fi

Receipt verification:

PR=<PR-number>
HEAD_SHA=$(gh pr view "$PR" --json headRefOid --jq .headRefOid)
RECEIPT=$(gh pr view "$PR" --json comments --jq '.comments | map(select(.body | contains("ICA-REVIEW-RECEIPT"))) | last | .body // ""')

echo "$RECEIPT" | rg -q "Reviewer-Stage: 3 \\(temp checkout\\)"
echo "$RECEIPT" | rg -q "Reviewer-Agent:.*\\(subagent\\)"
echo "$RECEIPT" | rg -q "Head-SHA: $HEAD_SHA"
echo "$RECEIPT" | rg -q "Findings: 0"
echo "$RECEIPT" | rg -q "NO FINDINGS"
echo "$RECEIPT" | rg -q "Result: PASS"

Merge (agent-performed):

gh pr merge <PR-number> --squash --delete-branch

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.