菜单
Analyze the current branch's diff from main and related PR to build context for followup requests. Triggers on "prepare context", "branch context", "catch me up", "what's on this branch".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | prepare-branch-context |
| description | Analyze the current branch's diff from main and related PR to build context for followup requests. Triggers on "prepare context", "branch context", "catch me up", "what's on this branch". |
| user-invocable | true |
Build a comprehensive understanding of the current branch so you can handle followup requests with full context.
Identify the current branch and base branch:
git branch --show-current
git merge-base HEAD main
Gather the diff from main:
git diff main...HEAD --stat
git diff main...HEAD
Read through the full diff carefully. Understand what files were changed, added, or removed, and what the changes do.
Review the commit history on this branch:
git log main..HEAD --oneline
Read commit messages to understand the progression of changes.
Check for a related PR:
gh pr list --head "$(git branch --show-current)" --json number,title,body,url,state,comments --jq '.[0]'
If a PR exists, read its title, description, and comments for additional context (acceptance criteria, discussion, review feedback).
Summarize your understanding to the user:
Signal readiness: Tell the user you're ready for followup questions or tasks related to this branch.
main or has no divergence from main, tell the user there's nothing to analyze.Reviews code changes for reuse, composition, codebase consistency, and slop. Use when asked to review PRs/diffs, check code reuse, composition, cleanliness, or whether code fits the codebase.
Commit, push, and create a draft PR using the pr-description format, with UX flow context when relevant.
Kick off follow-up work on an existing PR in a parallel tmux/agent session. Use when the user asks to work on a PR, continue a branch, address PR feedback, or resolve merge conflicts in the background.
Kick off a new feature or fix in a parallel clone with Pi working autonomously. Takes a problem description, generates a concise branch name, runs ga to set up the worktree, and sends a crafted prompt to the new Pi session.
Review or refactor code so the correct behavior is the default path; use when APIs, setters, hooks, helpers, or component props have footguns where a natural call bypasses required semantics.
Create UX-first plans as flow trees, then attach concrete function names, files, and implementation anchors after the high-level flow is clear.