Skip to content

mihaibojin/worktrees

v0.9.0Apache-2.0

Start branches, read CI, rebase onto the head branch, describe, ship and merge pull requests, and prune finished worktrees through the worktrees CLI

ci-checks

Read a pull request's or merge request's CI checks as compact JSON with gw ci-checks, and wait for them to finish. Use it whenever you need to know whether CI passed, which check failed, or when running checks finish, instead of gh pr checks, gh pr view --json statusCheckRollup, gh run list or glab ci status.

describe-pr

Check a pull request's or merge request's title and description against its diff and fix them when they are wrong. Run it, without being asked, right after opening a pull request, after pushing commits to a branch that has one open, and before merging one. Also when the user asks to write, check or fix a PR title, description or body.

fast-forward

Use when the user asks to bring a branch up to date with main or the head branch, rebase it onto the head branch, fast-forward it, move on from a merged or partly merged branch, or finish a rebase that gw fast-forward stopped at.

new-branch

Start a branch for new work from the freshly fetched head branch with gw branch create. Use when starting a task, a feature or a fix that needs its own branch, or when the user asks for a new branch.

preflight

Add the Claude Code permission rules this plugin's skills need beyond their own pre-approval to the user's or the project's settings.json, after showing every missing line and asking. Runs only when the user calls it by name.

prune

Assess git worktrees and loose local branches, then remove the finished ones the user approves. Use when the user asks to clean up, tidy or prune finished, merged or squash-merged worktrees or branches, or asks which are done.

ship-it

Take a change to a merged pull request or merge request, unassisted. With no arguments, the change in this checkout from uncommitted work: commit, bring the branch level with the head branch, push and open the review. With branch names, the same for each branch, in the worktree that holds it. With numbers, those open reviews, a stack bottom first. Then fix failing CI, merge, and report what was fixed. Use when the user asks to ship, merge or land a change, a branch or a pull request. With --hold-merge, stop before the merge and print the command that makes it.