Stacks
Stacked pull requests with the GitHub CLI `gh stack` extension. Trigger whenever the user wants to split a large branch or change into a chain of dependent PRs ("stack this into smaller PRs", "split this into a stack", "create a stacked PR", "break this feature into reviewable layers"), or manage an existing stack ("add a layer on top", "rebase my stack", "sync the stack after the bottom PR merged", "merge the stack"). Use this instead of the `pr` skill whenever the work involves more than one dependent PR or any `gh stack` command; use `pr` for single, standalone pull requests.
Install
/plugin marketplace add robbyt/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add robbyt/claude-skills --skill stacksgit clone --depth 1 https://github.com/robbyt/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/gh-cli/skills/stacks ~/.claude/skills/stacksPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Stacked Pull Requests via `gh stack` A **stack** is a chain of small PRs where each targets the branch below it, and the whole chain lands on a **trunk** (usually `main`). Instead of one giant diff, reviewers get focused, independently reviewable layers. This is the antidote to the un-reviewable "here's 4,000 lines of AI-generated code" PR. Use this skill for any multi-PR dependent chain or any `gh stack …` command. For a single standalone PR, use the `pr` skill instead. ## Preview status & constraints (read before you start) - **Public preview**, extension **`github/gh-stack` v0.1.0** (snapshot: 2026-08-02). Behavior may change — if a command or flag here doesn't match reality, run `gh stack <command> --help` and trust that. - **Trunk** = the base branch of the *bottom* PR. Defaults to the repo's default branch; set a different one with `--base`. - **Same-repository only** — no cross-fork stacks. Not supported in GitHub Desktop. - **Stack-base evaluation rule (surprising, important):** branch protection, required checks, CODEOWNERS, code scanning, and Actions are evaluated against the **stack base** (the trunk), *not* the branch directly below. Every mid-stack PR is held to the trunk's standard, and a PR merges only after every PR below it also passes. - **Linear history is mandatory** before merging. Closing a mid-stack PR blocks every PR above it. ## Assume the extension is installed
Details
- Skill name
stacks- Repository
- robbyt/claude-skills
- Path
plugins/gh-cli/skills/stacks/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Stacks skill do?
Stacked pull requests with the GitHub CLI `gh stack` extension. Trigger whenever the user wants to split a large branch or change into a chain of dependent PRs ("stack this into smaller PRs", "split this into a stack", "create a stacked PR", "break this feature into reviewable layers"), or manage an existing stack ("add a layer on top", "rebase my stack", "sync the stack after the bottom PR merged", "merge the stack"). Use this instead of the `pr` skill whenever the work involves more than one dependent PR or any `gh stack` command; use `pr` for single, standalone pull requests.
How do I install the Stacks skill?
Claude Code plugin: /plugin marketplace add robbyt/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Stacks popular?
It lives in robbyt/claude-skills, which has 42 GitHub stars and 2 forks.
Related skills
Actions
42robbyt/claude-skills
GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").
Adversarial Review
42robbyt/claude-skills
Have Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (
API Review
42robbyt/claude-skills
This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions",
View File
42robbyt/claude-skills
Fetch raw file content from GitHub URLs. Trigger when user shares a GitHub file link (https://github.com/user/repo/blob/main/file.go) and wants to view the source code. Avoids HTML/JS clutter from WebFetch.
Repo
42robbyt/claude-skills
Repository information using GitHub CLI. Trigger when user wants to view repository details ("show repo info", "what's this repo about"), list repositories ("list my repos", "show repos for user"), or check repository metadata ("stars", "languages", "topics").
Git Remote Publishing
44SamueleBassoli/hermes-fleet-apps
Use when preparing a repo's first public push or release.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.