github

957

callstackincubator

GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.

commit-hygiene

521

alinaqi

Atomic commits, PR size limits, commit thresholds, stacked PRs

jj

12

coreyja

Use Jujutsu (jj) for version control. Covers workflow, commits, bookmarks, pushing to GitHub, absorb, squash, and stacked PRs. Use when working with jj, creating commits, pushing changes, or managing version control.

managing-stacked-prs

11

josephschmitt

Manages stacked pull requests using git-spice. Creates smaller, reviewable PRs that build on each other, submits them for review, handles feedback, and maintains clean stack history. Use when working with git-spice, stacked PRs, or managing dependent branches.

git-rebase-patterns

10

laurigates

Advanced git rebase patterns for linear history, stacked PRs, and clean commit management. Use when rebasing branches, cleaning up commit history, managing PR stacks, or converting merge-heavy branches to linear history. Covers --reapply-cherry-picks, --update-refs, --onto, and interactive rebase workflows.

jj-workflow

4

Praveenperera Dotfiles Jj Workflow

Guide for jj (Jujutsu) version control workflows including splitting changes, creating stacked PRs, independent PRs, and hybrid approaches. Use when working with jj commands, feature branches, or preparing commits for pull requests.

github

4

Liinkiing

GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.

rebase-parent

1

flurdy

Rebase the current branch onto an updated parent PR branch. Use when you have stacked PRs and the parent branch has been updated (force-pushed after its own rebase or new commits added).

graphite

DerGut

Graphite CLI for commits, branches, pushes, PRs, and stacked diffs. This skill should be used when the user mentions Graphite, gt commands (gt create, gt modify, gt submit, gt sync, gt split, gt ss), stacked PRs, stacked diffs, or stacked branches. It should also be used when about to commit, push, or create a PR, or when evaluating whether the current changeset should be committed as-is or split into smaller pieces first. Relevant when deciding whether to continue adding changes to the current branch or start a new one, when working on top of un-merged branches, managing dependent PRs, or restacking branches.