New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Choruz Merging Stacked PRs

by inclusionAI in inclusionAI/Choruz

A skill your agent uses when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request…

Apache-2.0Auto-check passedDevelopment

Install Choruz Merging Stacked PRs

skills CLI
$ npx skills add inclusionAI/Choruz --skill choruz-merging-stacked-prs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install inclusionAI/Choruz choruz-merging-stacked-prs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/inclusionAI/Choruz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/choruz-merging-stacked-prs .claude/skills/choruz-merging-stacked-prs && rm -rf skills-src

Use ~/.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/

Facts

Skill name
choruz-merging-stacked-prs
GitHub stars
1k
Token cost
~866 tokens
SKILL.md length
462 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request…

  • Works in 2 steps: Require it open, non-draft, and CI… → Squash-merge it (the repository…
  • Landing a chain of dependent pull requests (A ← B ← C
  • SKILL.md covers Establish the chain, Land one layer, Do not and Verify the landed state, plus 1 more section
  • Calls gh and git

What it does

Choruz Merging Stacked PRs is an agent skill from inclusionAI/Choruz. Use when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request mentions "stacked PRs", "PR stack", "dependent PRs", or merging several related PRs in sequence.

Its SKILL.md is about 870 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 licence is Apache-2.0.

When your agent uses it

  • Landing a chain of dependent pull requests (A ← B ← C
  • Each based on the one below) onto main
  • Merging a PR whose base is another open PRs branch
  • Whenever a request mentions stacked PRs

Example prompts

  • “s branch, or whenever a request mentions”
  • “PR stack”
  • “dependent PRs”
  • “/choruz-merging-stacked-prs”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Require it open, non-draft, and CI (linux) required green on its exact current head. A green upper layer proves nothing about its…
  2. Squash-merge it (the repository convention). Do not delete the branch yet: the next layer still bases on it.

What it can do on your machine

Read from SKILL.md and the folder at commit 7509c40. 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:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and 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

Choruz Merging Stacked PRs loads about 866 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 462 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~866

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 inclusionAI/Choruz at commit 7509c40, republished under its Apache-2.0 licence (© inclusionAI). 462 words, ~866 tokens.

Download SKILL.mdSave it as .claude/skills/choruz-merging-stacked-prs/SKILL.md (or your agent's skills folder).
name
choruz-merging-stacked-prs
description
Use when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request mentions "stacked PRs", "PR stack", "dependent PRs", or merging several related PRs in sequence.

Landing a Choruz PR stack

A stack is a chain of pull requests where each upper PR's base is the head branch of the one below. Land it bottom-up, one green squash at a time, and let CI re-run against main before every merge. Never reproduce a stack by rewriting someone else's branch.

Establish the chain

Fetch current metadata for every PR rather than trusting branch names or an earlier report:

sh
gh pr view <pr> --json number,author,baseRefName,headRefName,headRefOid,state,isDraft,mergeStateStatus,statusCheckRollup

The bottom PR targets main; each higher PR targets the head branch immediately below. Any other shape (two PRs targeting the same branch, a cycle, a cross-fork head) needs the user's direction before any mutation. If GitHub's native stack feature (gh stack) is available and the chain is already linked, prefer gh stack merge for the whole range and skip to Verify the landed state; otherwise follow the manual sequence below.

Land one layer

For the bottom PR:

  1. Require it open, non-draft, and CI (linux) required green on its exact current head. A green upper layer proves nothing about its dependencies.
  2. Squash-merge it (the repository convention). Do not delete the branch yet: the next layer still bases on it.

For the next PR up:

  1. Retarget its base to main: gh pr edit <pr> --base main.
  2. Bring main in. Its branch already contains the lower branch's commits, and main now contains their squash; a merge resolves cleanly when nothing else touched the same lines: git merge --no-edit origin/main, then push. On a branch you created, a rebase is equally acceptable; on someone else's branch, only a merge commit.
  3. The push re-triggers CI against the real base. Wait for CI (linux) required on the new head, then squash-merge.

Repeat until the requested range has landed. "Land the stack" means every layer; a partial landing names an explicit boundary PR and stops there.

Show full SKILL.md (156 more words)Show less

Do not

  • Merge an upper layer before its base has merged, or while its base is still another PR's branch.
  • Force-push, rebase, or amend a branch you did not create.
  • Push an empty commit or close and reopen a PR to re-run CI; a base change plus git merge origin/main is the correct trigger.
  • Bypass a red or missing CI (linux) required on any layer.

Verify the landed state

Wait for every selected PR to report MERGED:

sh
gh pr view <pr> --json number,state,mergedAt,mergeCommit,baseRefName,headRefName

Delete branches only in a final pass after the corresponding PRs report MERGED and no open PR still uses the branch as a base:

sh
gh pr list --state open --base <branch> --json number --jq length   # must print 0

Checklist

  • Live PR bases and heads establish one bottom-to-top chain.
  • Each layer merged only when green on its exact head, bottom first.
  • Each upper layer retargeted to main and refreshed with main before its own CI run.
  • No branch rewritten that someone else created.
  • Every selected PR reports MERGED; branches deleted only after zero-dependent verification.

© inclusionAI, Apache-2.0. 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 .agents/skills/choruz-merging-stacked-prs of inclusionAI/Choruz.

Open the folder on GitHubat commit 7509c40

Compare with similar skills

Choruz Merging Stacked PRs 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.

Choruz Merging Stacked PRs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Choruz Merging Stacked PRs this skillinclusionAI/Choruz1k—~866Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • 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.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • 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.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • 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.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • 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…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • 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.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from inclusionAI/Choruz

All 11 skills in this repo

  • Choruz Archive Agent Notes

    inclusionAI/Choruz

    A skill your agent uses when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in this repository; checks every new note for superseded active records, classifies implemented…

    1k GitHub stars~1.2k tokensUpdated 4 days ago
    Auto-check passed

  • Choruz CI Test Reliability

    inclusionAI/Choruz

    Design, review, and diagnose Choruz tests and fixtures that can fail nondeterministically under CI concurrency: parallel Playwright workers sharing one PostgreSQL and one API, vitest workers, cargo…

    1k GitHub stars~1.8k tokensUpdated 4 days ago
    Auto-check passed

  • Choruz Code Review

    inclusionAI/Choruz

    A skill your agent uses when reviewing a pull request in this repository; orients the reviewer to Choruz's standards (AGENTS.md conventions, the PR test policy, Agent Notes, the CI gates) and the…

    1k GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check passed

  • Choruz Doc

    inclusionAI/Choruz

    Create, restructure, review, audit, or migrate Choruz Markdown documentation (docs/, README, AGENTS.md, the in-app docs pages) using one owner per fact, tier placement, executed-operation…

    1k GitHub stars~1.6k tokensUpdated 4 days ago
    Auto-check passed

  • Choruz Find Simplifications

    inclusionAI/Choruz

    A skill your agent uses when working in this repository to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or…

    1k GitHub stars~1.6k tokensUpdated 4 days ago
    Auto-check passed

  • Choruz PR

    inclusionAI/Choruz

    Use before opening or completing a pull request in this repository — classify the change, add the tests its type requires, run exactly what CI will run, label it, merge only on a green "CI (linux)…

    1k GitHub stars~2.6k tokensUpdated 4 days ago
    Auto-check passed

Categories

Questions about Choruz Merging Stacked PRs

What does Choruz Merging Stacked PRs do?

A skill your agent uses when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request…. Choruz Merging Stacked PRs is an agent skill from inclusionAI/Choruz. Use when landing a chain of dependent pull requests (A ← B ← C, each based on the one below) onto main, merging a PR whose base is another open PR's branch, or whenever a request mentions "stacked PRs", "PR stack", "dependent PRs", or merging several related PRs in sequence.

When should I use Choruz Merging Stacked PRs?

Choruz Merging Stacked PRs fits situations like: landing a chain of dependent pull requests (A ← B ← C; each based on the one below) onto main; merging a PR whose base is another open PRs branch; whenever a request mentions stacked PRs.

How do I install Choruz Merging Stacked PRs in Claude Code?

Run `npx skills add inclusionAI/Choruz --skill choruz-merging-stacked-prs -a claude-code`. Or copy the skill folder (.agents/skills/choruz-merging-stacked-prs in inclusionAI/Choruz) into .claude/skills/choruz-merging-stacked-prs in your project. Claude Code loads it when a task matches its description.

How do I install Choruz Merging Stacked PRs in Codex?

Run `npx skills add inclusionAI/Choruz --skill choruz-merging-stacked-prs -a codex`. Or copy the skill folder (.agents/skills/choruz-merging-stacked-prs in inclusionAI/Choruz) into .agents/skills/choruz-merging-stacked-prs in your project. Codex loads it when a task matches its description.

Can I use Choruz Merging Stacked PRs 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 inclusionAI/Choruz --skill choruz-merging-stacked-prs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/choruz-merging-stacked-prs, .gemini/skills/choruz-merging-stacked-prs, .github/skills/choruz-merging-stacked-prs and .opencode/skills/choruz-merging-stacked-prs in your project.

What does Choruz Merging Stacked PRs need to run?

Going by SKILL.md and its folder, Choruz Merging Stacked PRs needs the command-line tools its instructions call (gh and git).

Does Choruz Merging Stacked PRs access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Choruz Merging Stacked PRs 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 Choruz Merging Stacked PRs use?

Choruz Merging Stacked PRs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Choruz Merging Stacked PRs use?

About 866 tokens (SKILL.md is roughly 3.5k 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 Choruz Merging Stacked PRs?

Skills that share tags, products or a category with Choruz Merging Stacked PRs: 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 Choruz Merging Stacked PRs?

inclusionAI (a GitHub organization) maintains it in inclusionAI/Choruz, which has 1,017 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

Source: inclusionAI/Choruz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.