Use cases
Where stacked diffs earn their keep.
Stacked diffs aren't for every change — a one-line fix is still a one-line PR. But when work is big, dependent, or blocked, this is where stkd pays off.
Feature developers
Ship large features as small, reviewable PRs
Break a 2,000-line feature into a chain of focused PRs your team can actually review — and keep coding while each one waits.
Read the use case →Fast-moving teams
Stop blocking teammates on review latency
Don't idle waiting for a review. Stack the next change on top of the pending one and let stkd keep both in sync.
Read the use case →AI-assisted teams
Let AI agents drive stacked pull requests
Give Claude Code, Cursor, and other MCP agents typed tools to create branches, submit stacks, and resolve conflicts — no fragile shell-outs.
Read the use case →GitLab shops
Bring stacked diffs to GitLab and self-hosted GitLab
Most stacked-diff tools are GitHub-only. stkd treats GitLab merge requests — including self-hosted instances — as a first-class peer.
Read the use case →Ready to stack your next change?
Install stkd in under a minute. Apache-2.0, single binary, every major platform.