Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
Install PR Merge Champion
$ npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills pr-merge-champion --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-merge-champion .claude/skills/pr-merge-champion && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-merge-champion" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/pr-merge-champion into .claude/skills/pr-merge-champion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-merge-champion", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/pr-merge-championType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills pr-merge-champion --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pr-merge-champion .agents/skills/pr-merge-champion && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-merge-champion" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/pr-merge-champion into .agents/skills/pr-merge-champion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-merge-champion", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills pr-merge-champion --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pr-merge-champion .cursor/skills/pr-merge-champion && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-merge-champion" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/pr-merge-champion into .cursor/skills/pr-merge-champion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-merge-champion", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/pr-merge-champion--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills pr-merge-champion --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pr-merge-champion .gemini/skills/pr-merge-champion && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-merge-champion" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/pr-merge-champion into .gemini/skills/pr-merge-champion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-merge-champion", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills pr-merge-championInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pr-merge-champion .github/skills/pr-merge-champion && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-merge-champion" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/pr-merge-champion into .github/skills/pr-merge-champion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-merge-champion", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills pr-merge-champion --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pr-merge-champion .opencode/skills/pr-merge-champion && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-merge-champion" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/pr-merge-champion into .opencode/skills/pr-merge-champion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-merge-champion", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-merge-champion- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 566 words
- Files
- 1
- Skills in repo
- 1,497
- Repo updated
- First seen
- Licence
- MIT
At a glance
Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
- Works in 4 steps: Pre-Flight Clean Up & Rebase → Critical Self-Review → Local Verification & Test Suite → …
- Tasks that involve Pull requests
- SKILL.md covers Overview, When to Use This Skill, How It Works and Examples, plus 4 more sections
- Calls git
What it does
PR Merge Champion is an agent skill from sickn33/agentic-awesome-skills. Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “/pr-merge-champion”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
PR Merge Champion loads about 1.3k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 566 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 566 words, ~1,308 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-merge-champion/SKILL.md (or your agent's skills folder).- name
- pr-merge-champion
- description
- Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
- category
- workflow
- risk
- safe
- source
- self
- source_type
- self
- date_added
- 2026-06-16
- author
- himanshu-2l
- tags
- git, github, pull-request, code-review, workflow
- tools
- claude, cursor, gemini, antigravity
PR Merge Champion
Overview
A systematic playbook for preparing, reviewing, and documenting pull requests to ensure they are high-quality, free of common oversights, and optimized for instant maintainer approval and merging.
When to Use This Skill
- Use when preparing to open a new pull request on GitHub or any Git hosting platform.
- Use when self-auditing a feature or bug-fix branch for code cleanliness and consistency.
- Use when trying to minimize review cycles and speed up the integration of your changes.
How It Works
Step 1: Pre-Flight Clean Up & Rebase
Before presenting your code to reviewers, clean up any workspace noise and ensure your branch is up to date:
- Rebase your feature branch on top of the latest target branch (e.g.,
mainormaster) to resolve conflicts early. - Clean up untracked, temp, or swap files from your repository.
- Run local linters, formatters, and compilers to ensure no stylistic or syntax errors exist.
Step 2: Critical Self-Review
Review your own diff line-by-line as if you were the reviewer. Look out for:
- Leftover debugging statements (e.g.,
console.log,print, breakpoints, or custom debug flags). - Unnecessary changes, white-space only diffs, or commented-out code blocks.
- Incomplete
TODOcomments that should be resolved or turned into tracked issues. - Correctness of error handling and edge cases.
Step 3: Local Verification & Test Suite
Verify that all changes work as expected:
- Run the project's automated test suite locally to verify no regressions are introduced.
- Check test coverage for any new code blocks you added.
- Manually test the critical paths and edge cases of your feature or bug fix.
Step 4: Crafting the Pull Request Description
Write a high-signal, structured PR description. A great description tells the story of the changes:
- Summary: A concise explanation of the changes.
- Context / Why: Why this change is necessary and what problem it solves.
- Verification: Explicit details on how you tested it (test commands, screenshots, or step-by-step reproduction).
- Checklist: Conform to the repository's contributing guidelines and checklist requirements.
Examples
Show full SKILL.md (228 more words)Show less
Example 1: Creating a Clean PR Description
# Pull Request: Implement Rate Limiting on Authentication Endpoint
## Summary
Introduces an IP-based rate limiter on the `/api/v1/auth/login` endpoint using Redis to prevent brute-force attacks.
## Why
We identified a high volume of login attempts targeting single accounts. This rate limiting window slows down attackers while keeping the system responsive for genuine users.
## Verification
- Ran unit tests: `npm run test tests/auth.test.js` (all green)
- Manually verified using Postman: sending 15 requests in under 60 seconds returns `429 Too Many Requests`.
## Checklist
- [x] Code follows the style guide
- [x] Unit tests added/updated
- [x] Documentation updatedExample 2: Self-Review Clean Up Commands
Before committing, run these commands to inspect the diff for accidental additions:
# Check the names of files changed to ensure no unwanted files are staged
git status --porcelain
# Review the actual diff for any leftover print statements or debuggers
git diff | grep -E "(console\.log|debugger|print\(|var_dump|binding\.pry)"Best Practices
- ✅ Keep PRs Small and Focused: A PR with fewer than 200 lines of changes gets reviewed and merged significantly faster than a large one.
- ✅ Perform a Self-Review first: Finding your own bugs and formatting issues first builds trust with the maintainers.
- ✅ Respect Repository Guidelines: Check the project's
CONTRIBUTING.mdand pull request templates, and adhere to them strictly. - ❌ Do Not Bundle Unrelated Changes: Avoid sneaking refactoring or unrelated bug fixes into a feature PR. Create separate PRs instead.
- ❌ Do Not Ignore CI Failures: Always fix failing tests, linters, or security scans on your branch before requesting a review.
Limitations
- This skill does not replace project-specific CI/CD validation, automated testing, or domain-expert reviews.
- It assumes a standard Git and GitHub-like environment, though the core principles apply to GitLab, Bitbucket, and other platforms.
Common Pitfalls
- Problem: A PR is left open for a long time due to minor formatting or style comments. Solution: Always run the repository's local formatter (e.g., Prettier, ESLint, Black) before committing.
- Problem: Merge conflicts occur immediately after opening the PR. Solution: Pull the latest main branch and rebase or merge it into your branch daily.
Related Skills
@pr-writer- For Sentry-specific PR writing guidelines.@clean-code- To ensure code quality before submitting.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/pr-merge-champion of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
PR Merge Champion next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PR Merge Champion this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 91k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
More from sickn33/agentic-awesome-skills
All 1,497 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Categories
Questions about PR Merge Champion
What does PR Merge Champion do?
Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation. PR Merge Champion is an agent skill from sickn33/agentic-awesome-skills. Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.
When should I use PR Merge Champion?
PR Merge Champion fits situations like: tasks that involve Pull requests.
How do I install PR Merge Champion in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a claude-code`. Or copy the skill folder (skills/pr-merge-champion in sickn33/agentic-awesome-skills) into .claude/skills/pr-merge-champion in your project. Claude Code loads it when a task matches its description.
How do I install PR Merge Champion in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a codex`. Or copy the skill folder (skills/pr-merge-champion in sickn33/agentic-awesome-skills) into .agents/skills/pr-merge-champion in your project. Codex loads it when a task matches its description.
Can I use PR Merge Champion in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill pr-merge-champion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-merge-champion, .gemini/skills/pr-merge-champion, .github/skills/pr-merge-champion and .opencode/skills/pr-merge-champion in your project.
What does PR Merge Champion need to run?
Going by SKILL.md and its folder, PR Merge Champion needs the command-line tools its instructions call (git).
Does PR Merge Champion access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Merge Champion safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does PR Merge Champion use?
PR Merge Champion is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR Merge Champion use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to PR Merge Champion?
Skills that share tags, products or a category with PR Merge Champion: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Merge Champion?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.