checkout
Use when checking out a PR, branch, or ref for local work - sets up worktree with context
Install
npx skills add https://github.com/technicalpickles/pickled-claude-plugins/tree/main/plugins/git/skills/checkout
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install technicalpickles-pickled-claude-plugins@llmmart
git clone https://github.com/technicalpickles/pickled-claude-plugins.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole technicalpickles/pickled-claude-plugins collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Git Checkout
Check out a PR, branch, or ref into an isolated worktree, with the context needed to start work or review.
Accepts a PR URL, {repo}#{number}, #{number} or a bare number (infer owner/repo from the git remote), a branch name, or a SHA/tag.
PRs
gh pr view <number> --json title,body,author,state,baseRefName,headRefName,url,reviews,reviewRequestsgit fetch origin <headRefName>before creating the worktree.- Create the worktree with
superpowers:using-git-worktrees, which picks the directory and honors the user's worktree tool. Name itpr-<number>-<2-3-word-description>(e.g.pr-1234-add-oauth). - Report: title, author,
head -> base, full URL, a 1-3 sentence summary of the PR body, changed files grouped by directory, review status (existing reviews, requested reviewers), and the worktree path.
Branches and refs
Create the worktree the same way (new branch if it doesn't exist yet) and report the path and branch.
Related
git:inboxto find PRs awaiting review,code-reviewfor the review itself.
Files (pickled-claude-plugins)
-
SKILL.md 1.2 KB
--- name: checkout description: Use when checking out a PR, branch, or ref for local work - sets up worktree with context --- # Git Checkout Check out a PR, branch, or ref into an isolated worktree, with the context needed to start work or review. Accepts a PR URL, `{repo}#{number}`, `#{number}` or a bare number (infer owner/repo from the git remote), a branch name, or a SHA/tag. ## PRs 1. `gh pr view <number> --json title,body,author,state,baseRefName,headRefName,url,reviews,reviewRequests` 2. `git fetch origin <headRefName>` before creating the worktree. 3. Create the worktree with `superpowers:using-git-worktrees`, which picks the directory and honors the user's worktree tool. Name it `pr-<number>-<2-3-word-description>` (e.g. `pr-1234-add-oauth`). 4. Report: title, author, `head -> base`, full URL, a 1-3 sentence summary of the PR body, changed files grouped by directory, review status (existing reviews, requested reviewers), and the worktree path. ## Branches and refs Create the worktree the same way (new branch if it doesn't exist yet) and report the path and branch. ## Related - `git:inbox` to find PRs awaiting review, `code-review` for the review itself.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.