메뉴
Creates a new git branch for current or proposed changes, deriving a conventional name when none is given. Use when the user wants to start a branch, e.g. `/branch <name?>`.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | branch |
| description | Creates a new git branch for current or proposed changes, deriving a conventional name when none is given. Use when the user wants to start a branch, e.g. `/branch <name?>`. |
| user-invocable | true |
| disable-model-invocation | false |
Create a new git branch for the current changes or proposed work, using the supplied name or deriving one from the change content.
Branch names use a conventional type prefix (feat/, fix/, chore/, docs/, ci/, style/, refactor/, test/, perf/, build/).
Base new branches on a fresh default branch tip; never discard or commit existing work as a side effect.
Follow CLAUDE.md / AGENTS.md on conflict.
name (with or without a type prefix).git status --short and git diff --stat to capture the current change context.name is given, use it; add a type prefix only when it lacks one.<type>/<slug> from the change content or the user's description.feat, fix, chore, docs, ci, style, refactor, test, perf, build).git checkout -b <name>, basing it on a fresh origin/HEAD when current work should not carry over; keep uncommitted changes when they belong on the new branch.Stop and ask if the name is ambiguous, collides with an existing branch, or the intended base is unclear.
origin/HEAD.Report the new branch name, its base ref, whether the name was supplied or derived, and the chosen type prefix.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Splits a large branch or PR into smaller, independently reviewable units by grouping changes and proposing parallel PRs or a stacked series. Use when a changeset is too big to review well and should be broken up.
Captures the portable, non-secret pi config from a live ~/.pi/agent into this repo's pi/ directory and commits it, without reading or copying secrets. Use when live pi config or extensions have drifted from the repo and need to be synced back.
Refreshes PR titles and descriptions to match the current branch changeset. Use when the PR title or body has drifted from the code.
Reviews the current session for problems and their eventual fixes, then proposes durable improvements to repo skills, scripts, or docs that prevent recurrence. Use when a session hit avoidable friction worth turning into a lasting fix.
Runs discovery and uncertainty resolution for a change, then writes a terse plan document covering purpose, behaviour, validation, architecture, and phased vertical slices. Use before building when a change needs a clear, agreed design.