agentbro-pr-merge

AgentBro PR Merge

Use this skill for AgentBro pull request triage and merge work.

Rules

• Start with git status --short --branch.
• PRs should target dev unless the maintainer explicitly says otherwise.
• Do not merge while required checks are failing or missing.
• For external contributor PRs, prefer Squash and merge into dev so GitHub can attribute the squash commit to the PR author.
• Do not squash dev into main during release. Release merges should preserve commits with git merge --no-ff origin/dev.
• If a fork PR has maintainerCanModify: true, small mechanical fixes may be pushed to the contributor branch. Keep them scoped and explain them.

Standard Flow

1. Inspect the PR:

gh pr view <number> --repo shirenchuang/agentbro \
  --json number,title,author,baseRefName,headRefName,headRepositoryOwner,maintainerCanModify,isDraft,mergeable,mergeStateStatus,statusCheckRollup,commits,files

1. Confirm contribution attribution:

gh pr view <number> --repo shirenchuang/agentbro --json author,commits \
  --jq '{author:.author.login, commits:[.commits[] | {oid:.oid[0:7], authors:.authors}]}'

If commit authors do not map to the PR author, squash merge is the safer path.

1. If GitHub Actions is action_required, approve it only after checking that the PR did not modify workflows or sensitive release/signing files:

gh api --method POST repos/shirenchuang/agentbro/actions/runs/<run-id>/approve

1. If CI fails, fix only narrow mechanical issues unless the user asks for deeper review. For fork PRs:

gh pr checkout <number> --repo shirenchuang/agentbro
# make the small fix
git push https://github.com/<fork-owner>/agentbro.git HEAD:<head-branch>

1. Wait for checks:

gh run watch <run-id> --repo shirenchuang/agentbro --interval 10 --exit-status
gh pr checks <number> --repo shirenchuang/agentbro

1. Merge only when clean:

gh pr merge <number> --repo shirenchuang/agentbro --squash