Loading...
Loading...
Found 7 Skills
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
Use the gh-stackx gh extension to submit, sync, and merge stacked pull requests when the GitHub Stacked PRs API is unavailable.
Use for stacked PRs with the gh-stack extension: creating, viewing, editing, pushing, submitting, syncing, rebasing, merging, or checking out a stack, or splitting multi-part work into reviewable layers. Also use whenever a stack is checked out or the user mentions stacks, branch layers, or dependent PRs.
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
Use when asked to "merge all open PRs" or land the open PRs together. Snapshots the open set, builds one gh stack, resolves conflicts, and merges once.
Organize checkout/worktree topology, dependent branch/PR stacks, and unified delivery boundaries for change workstreams using Git/GitHub: identify normalized repositories and isolate regular implementations with an owning worktree by default, with worktree also permitted by default for explicit PR requests; determine commit, push, and PR actions in order of user-specified explicit endpoints, default Draft PR for normalized repositories, and local-only default for non-normalized repositories; publish safely from main/master; follow up on conflicts, CI status, and local commit/push for existing PRs. Applicable to worktree creation, migration, secure cleanup, "branch already checked out" scenarios, post-implementation Git delivery, splitting stacked/dependent PRs, using `gh stack` to create, view, sync, or land stacks, as well as PR merge conflicts, failed checks, fixing PRs to mergeable state, and uncommitted or unpushed fixes. It only owns Git topology and delivery, and does not take over domain implementation or project design; the exact syntax of `gh stack` is discovered from local `--help` output. Default delivery does not grant authorization to implicitly switch the main working tree branch, mark as Ready, merge, retarget, release, or force-push.