How do I install the Agentbro Pr Merge skill?

Run npx skillmds@latest add shirenchuang/agentbro-pr-merge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agentbro Pr Merge safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agentbro Pr Merge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agentbro Pr Merge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agentbro Pr Merge?

shirenchuang (@shirenchuang) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agentbro Pr Merge by shirenchuang — Agent Skill

Name: Agentbro Pr Merge
Author: shirenchuang

File contents

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

Inspect the PR:

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

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.

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

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>

Wait for checks:

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

Merge only when clean:

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

Verify:

gh pr view <number> --repo shirenchuang/agentbro --json state,mergedAt,mergeCommit
gh api repos/shirenchuang/agentbro/commits/<merge-sha> --jq '{author:.author.login, raw_author:.commit.author}'

The repository homepage may not show the contributor until the commit reaches the default branch (main) and GitHub updates its cache.

---name: agentbro-pr-mergedescription: Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.---# AgentBro PR MergeUse 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 Flow1. Inspect the PR:```bashgh pr view <number> --repo shirenchuang/agentbro \ --json number,title,author,baseRefName,headRefName,headRepositoryOwner,maintainerCanModify,isDraft,mergeable,mergeStateStatus,statusCheckRollup,commits,files```2. Confirm contribution attribution:```bashgh 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.3. If GitHub Actions is `action_required`, approve it only after checking that the PR did not modify workflows or sensitive release/signing files:```bashgh api --method POST repos/shirenchuang/agentbro/actions/runs/<run-id>/approve```4. If CI fails, fix only narrow mechanical issues unless the user asks for deeper review. For fork PRs:```bashgh pr checkout <number> --repo shirenchuang/agentbro# make the small fixgit push https://github.com/<fork-owner>/agentbro.git HEAD:<head-branch>```5. Wait for checks:```bashgh run watch <run-id> --repo shirenchuang/agentbro --interval 10 --exit-statusgh pr checks <number> --repo shirenchuang/agentbro```6. Merge only when clean:```bashgh pr merge <number> --repo shirenchuang/agentbro --squash```7. Verify:```bashgh pr view <number> --repo shirenchuang/agentbro --json state,mergedAt,mergeCommitgh api repos/shirenchuang/agentbro/commits/<merge-sha> --jq '{author:.author.login, raw_author:.commit.author}'```The repository homepage may not show the contributor until the commit reaches the default branch (`main`) and GitHub updates its cache.

Frequently asked questions

Agentbro Pr Merge