A branch-repair command that reapplies branches onto their current parent commits. It is a focused form of rebasing for a stack of dependent branches.

Use it to repair the current stack, only the branches above or below the current one, or just the current branch.

It fixes branches that still point to old commits after a merge, sync, or history change, and provides a way to continue or cancel conflict resolution.

restack — Command for Claude Code by pleaseai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/pleaseai/claude-code-plugins

Made for: Claude Code.

Or install graphite, the plugin that ships this one along with the rest of its 3 skills, 16 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/restack/github.svg)](https://agentmods.dev/commands/pleaseai/claude-code-plugins/restack)

Your own site

<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/restack"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/restack/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/restack"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/restack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 445 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00016	$0.00445
Opus 5	$0.00008	$0.00222
Sonnet 5	$0.00003	$0.00089
Haiku 4.5	$0.00002	$0.00044

Measured yesterday against content hash 9f4958b6a9c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

restack scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/graphite/commands/restack.md · 36 lines

What it actually says

Repair the stack when branches point at stale parent commits. User input: $ARGUMENTS.

When restack is needed

gt sync reported "could not restack" for one or more branches.
A PR was squash-merged on GitHub — children still reference the pre-squash SHA.
A manual git rebase was run on a tracked branch (avoid this in general).
gt ls shows needs restack next to a branch.

Steps

Run gt ls to identify branches marked needs restack.
If a specific branch was named in conflict output, gt co <branch> first.
Run the appropriate scope:
- gt restack — restack the current stack on its current parents.
- gt restack -u / --upstack — only branches above the current one.
- gt restack -d / --downstack — only branches below the current one.
- gt restack -o / --only — current branch only, leave neighbors.
On conflict during the rebase:
- Resolve conflicts in editor (markers <<<<<<< / ======= / >>>>>>>).
- gt add . to mark resolved (wraps git add).
- gt continue -a to finish the restack chain.
- Or gt abort to back out — safe to do.
After clean restack, run gt ls to confirm and consider gt submit --stack -u to update the PRs.

Notes

gt restack is idempotent — running it on an already-clean stack is a no-op.
Across worktrees: run gt restack from each worktree that owns branches in the stack (Graphite 1.8.4+).

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 36 lines · 16 tokens per session scan A 9f4958b6a9c6

Subscribe to this mod's changes

restack is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 445 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.

Git and workflow

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

restack