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.
Take commits from a sibling checkout as patches, without a fetch.
Install Sibling Checkout Commits
$ npx skills add JetBrains/intellij-community --skill sibling-checkout-commits -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/intellij-community sibling-checkout-commits --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/JetBrains/intellij-community.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sibling-checkout-commits .claude/skills/sibling-checkout-commits && 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 "sibling-checkout-commits" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/sibling-checkout-commits into .claude/skills/sibling-checkout-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sibling-checkout-commits", 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/JetBrains/intellij-community/tree/master/.agents/skills/sibling-checkout-commitsType 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 JetBrains/intellij-community --skill sibling-checkout-commits -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/intellij-community sibling-checkout-commits --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/sibling-checkout-commits .agents/skills/sibling-checkout-commits && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sibling-checkout-commits" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/sibling-checkout-commits into .agents/skills/sibling-checkout-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sibling-checkout-commits", 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 JetBrains/intellij-community --skill sibling-checkout-commits -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/intellij-community sibling-checkout-commits --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/sibling-checkout-commits .cursor/skills/sibling-checkout-commits && 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 "sibling-checkout-commits" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/sibling-checkout-commits into .cursor/skills/sibling-checkout-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sibling-checkout-commits", 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/JetBrains/intellij-community.git --path .agents/skills/sibling-checkout-commits--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 JetBrains/intellij-community --skill sibling-checkout-commits -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/intellij-community sibling-checkout-commits --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/sibling-checkout-commits .gemini/skills/sibling-checkout-commits && 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 "sibling-checkout-commits" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/sibling-checkout-commits into .gemini/skills/sibling-checkout-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sibling-checkout-commits", 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 JetBrains/intellij-community sibling-checkout-commitsInstalls 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 JetBrains/intellij-community --skill sibling-checkout-commits -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/sibling-checkout-commits .github/skills/sibling-checkout-commits && 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 "sibling-checkout-commits" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/sibling-checkout-commits into .github/skills/sibling-checkout-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sibling-checkout-commits", 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 JetBrains/intellij-community --skill sibling-checkout-commits -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JetBrains/intellij-community sibling-checkout-commits --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/sibling-checkout-commits .opencode/skills/sibling-checkout-commits && 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 "sibling-checkout-commits" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/sibling-checkout-commits into .opencode/skills/sibling-checkout-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sibling-checkout-commits", 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
sibling-checkout-commits- GitHub stars
- 21k
- Token cost
- ~753 tokens
- SKILL.md length
- 485 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Take commits from a sibling checkout as patches, without a fetch.
- Works in 4 steps: Find the range in the sibling. The base… → From the root of the receiving checkout… → Read the ok lines. Each one names the… → …
- Development work in your project
- SKILL.md covers Why not fetch, Procedure, What the script does, and does… and When a patch does not apply
- Runs Shell scripts from its folder; calls git
What it does
Sibling Checkout Commits is an agent skill from JetBrains/intellij-community, published by the product's own GitHub organization. Take commits from a sibling checkout as patches, without a fetch.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/take-patches.sh`).
It sits in Development. It works with Git. The repository describes itself as: IntelliJ IDEA & IntelliJ Platform.
When your agent uses it
- Development work in your project
Example prompts
- “/sibling-checkout-commits”
Requirements
- A Bash shell
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Find the range in the sibling. The base is the last sibling commit this checkout already has; a commit taken
- From the root of the receiving checkout run the script. It writes the patches under out/sibling-patches/,
- Read the ok lines. Each one names the new commit and confirms that its patch id equals the patch. A DIFF line
- On a weekend, the committer date is today: apply the weekend rule of the personal CLAUDE.md to the new commits.
What it can do on your machine
Read from SKILL.md and the folder at commit 06e4175. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
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
Sibling Checkout Commits loads about 753 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 485 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); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 485 words (~753 tokens).
“Use this skill when another checkout of the monorepo on this machine holds commits that this checkout needs, for example a reorganization that a new change builds on. The user keeps the checkouts separate, so a clone, a worktree or…”
- name
- sibling-checkout-commits
Files
SKILL.md and 1 other file (scripts) in .agents/skills/sibling-checkout-commits of JetBrains/intellij-community.
- SKILL.md
- scripts/take-patches.sh
Open the folder on GitHubat commit 06e4175
Compare with similar skills
Sibling Checkout Commits 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 |
|---|---|---|---|---|---|---|
| Sibling Checkout Commits this skillJetBrains/intellij-community | 21k | — | ~753 | Automated safety check: Pass | Custom licence | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 34 repos | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
More from JetBrains/intellij-community
All 39 skills in this repo- Official
Youtrack Community
JetBrains/intellij-community
YouTrack CLI for a community checkout; the monorepo uses youtrack.
- Official
Compare Python Typecheckers
JetBrains/intellij-community
Compare Python type inference with ty, pyrefly, and basedpyright.
- Official
Code Style
JetBrains/intellij-community
Apply IntelliJ Kotlin and Java code style when writing or reviewing.
- Official
Notebook For Experiment
JetBrains/intellij-community
Create reproducible Jupyter notebooks for performance experiments.
- Official
Jewel Markdown
JetBrains/intellij-community
Build or debug Jewel Markdown parsing, rendering, and styling.
- Official
Modcommand Migration
JetBrains/intellij-community
Convert LocalQuickFix or IntentionAction to the ModCommand API.
Related
Works with
Categories
Questions about Sibling Checkout Commits
What does Sibling Checkout Commits do?
Take commits from a sibling checkout as patches, without a fetch. Sibling Checkout Commits is an agent skill from JetBrains/intellij-community, published by the product's own GitHub organization. Take commits from a sibling checkout as patches, without a fetch.
When should I use Sibling Checkout Commits?
Sibling Checkout Commits fits situations like: development work in your project.
How do I install Sibling Checkout Commits in Claude Code?
Run `npx skills add JetBrains/intellij-community --skill sibling-checkout-commits -a claude-code`. Or copy the skill folder (.agents/skills/sibling-checkout-commits in JetBrains/intellij-community) into .claude/skills/sibling-checkout-commits in your project. Claude Code loads it when a task matches its description.
How do I install Sibling Checkout Commits in Codex?
Run `npx skills add JetBrains/intellij-community --skill sibling-checkout-commits -a codex`. Or copy the skill folder (.agents/skills/sibling-checkout-commits in JetBrains/intellij-community) into .agents/skills/sibling-checkout-commits in your project. Codex loads it when a task matches its description.
Can I use Sibling Checkout Commits 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 JetBrains/intellij-community --skill sibling-checkout-commits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sibling-checkout-commits, .gemini/skills/sibling-checkout-commits, .github/skills/sibling-checkout-commits and .opencode/skills/sibling-checkout-commits in your project.
What does Sibling Checkout Commits need to run?
Going by SKILL.md and its folder, Sibling Checkout Commits needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.
Does Sibling Checkout Commits 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 Sibling Checkout Commits 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Sibling Checkout Commits use?
Sibling Checkout Commits has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Sibling Checkout Commits use?
About 753 tokens (SKILL.md is roughly 3k 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 Sibling Checkout Commits?
Skills that share tags, products or a category with Sibling Checkout Commits: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sibling Checkout Commits?
JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/intellij-community, which has 20,619 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 10, 2026.
Source: JetBrains/intellij-community on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.