stacked-prs
From the author
Split large changes into reviewable stacked pull requests, maintain fixes in their owning slice, and land the stack in dependency order. Use when splitting a large branch or PR, updating a PR stack after review, carrying fixes through dependent branches, or merging stacked PRs on GitHub, GitLab, Bitbucket, or another Git host.
Install
npx skills add hashgraph-online/awesome-codex-plugins --skill stacked-prs -a claude-code
Installs to .claude/skills/stacked-prs/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- stack-reviewapache/magpieReview a GitHub stacked pull request as one unit on `<upstream>`: resolve the stack from any member PR or its stack number, check that the chain is linear and current, map every file to the layers that touch it, trace definitions removed in one layer and still used in another, and read code by tier with a coverage table instead of line by line. Drafts one rolling `COMMENT` on the lowest open layer and names the layers that deserve a `pr-management-code-review` pass. Never approves.Engineering★ 126
- gh-stackCherryHQ/cherry-studioManage Cherry Studio stacked branches and pull requests with the GitHub gh-stack extension. Use for planning, creating, inspecting, rebasing, syncing, linking, or recovering a stack of dependent PRs.Planning★ 53K
- stack-pushathola/claude-night-marketPushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice.Other★ 343
- pr-reviewoliver-kriska/claude-elixir-phoenixAddress feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.Engineering★ 571
- review-prtobihagemann/turboReview a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".Engineering★ 416
- git-branchlessOutlineDriven/outline-driven-developmentUse when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.Engineering★ 54
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in