메뉴
Create a git feature branch named for the current session's work. Slugifies the git username and derives a short kebab-case feature slug from the changes or task under discussion. Use when the user asks to start, create, or cut a branch.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write an implementation plan to docs/plans/. ALWAYS use this skill — never hand-roll a plan by mimicking files in docs/. Use when the user wants to create a project/implementation plan, when a plan discussed in chat should be persisted, or says /project-plan. Guarantees a spec exists, invoking to-spec if absent. Decomposes into vertical slices with Blocked-by edges, points to the spec for acceptance criteria, and extracts ADRs via to-adr.
Parse test failure output and diagnose root causes in a read-only background subagent, then fix the failures interactively in the main thread. Use when the user shares test output or says "tests fail". Default output path is /tmp/output.
Surface systemic patterns from an investigation as codified conventions or anti-patterns.
Architect a change from idea to actionable artifacts — bootstrap project instructions, research deeply, write a spec, then an implementation plan, each delegated to its skill. Use when the user wants to research a topic, explore a repo, write a spec, create a project plan, or says /architect.
Research a topic or repository deeply and produce a reference document under `docs/research/`. Handles two modes: code research (repo by URL, `org/repo`, or bare name — e.g. "check the spotless repo", "look at github.com/fastly/spotless") and topic research (concepts, technologies, patterns). Use when the user wants to research something, explore a repo, or says /research.
Elicit the user's intent before starting work. Use when a request is vague, when kicking off a new task, when another skill hits a vague request and needs to clarify it, or when the user says "help me with this", "I need something", "let's work on...", "draft a task", or /task.
| name | branch |
| description | Create a git feature branch named for the current session's work. Slugifies the git username and derives a short kebab-case feature slug from the changes or task under discussion. Use when the user asks to start, create, or cut a branch. |
| allowed-tools | Bash(git branch:*), Bash(git config:*), Bash(git status:*), Bash(git switch:*), Bash(git symbolic-ref:*) |
Create a feature branch named <git-username>/<feature-slug>, off
the current base branch, using the session context to name it.
If the fields below show commands rather than output, run each one first.
git branch --show-current 2>/dev/null || echo "(not a git repo)"git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo "(unknown)"git config user.name 2>/dev/null || echo "(unset)"git status --short 2>/dev/nullCheck the current branch.
main/master or the repo's
default branch) → stop and report it. Don't nest a branch off
another feature branch unless the user explicitly asks.Derive the username segment. Slugify git config user.name
so spaces and other non-alphanumeric characters become hyphens
(e.g. "First Last" → first-last):
git_username=$(git config user.name \
| tr '[:upper:]' '[:lower:]' \
| sed -E 's/[^a-z0-9]+/-/g; s/^-+|-+$//g')
If user.name is unset, ask the user for the segment.
Derive the feature slug from session context. A short,
kebab-case description of the work (e.g. fix-login-redirect).
Draw it, in order of preference, from:
Keep it concise — a few words, lowercase, hyphen-separated, no type prefix. If the intent is unclear or you'd be guessing, propose a slug and confirm before creating the branch.
Create the branch:
git switch -c "${git_username}/<feature-slug>"
Report the new branch name.