Menu
Create a traceable Git branch for the current task.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Break a spec, brief, issue tracker item, or user request into agent-sized tasks, using phases and milestones only when they clarify larger work, delivered to exactly one destination.
Bootstrap a new or empty project repository with a local skeleton: README, license, .gitignore, AGENTS.md, docs, and optional commit or push only when explicit. Interview the repo creator when file-changing decisions are unclear.
Verify browser-rendered work in a real browser. Use for HTML, UI, visual docs, presentations, local apps, and browser-facing changes.
Stage intended changes and create one Conventional Commit.
Find and fix the root cause when something breaks: a failing test, a broken build, a bug report, or behavior that doesn't match expectations. Use when the user says 'debug', 'why is this failing', 'fix this bug', or when a failure interrupts other work.
Write a lightweight technical design document for ambiguous or consequential architecture decisions before implementation.
| name | branch |
| description | Create a traceable Git branch for the current task. |
| user-invocable | true |
| argument-hint | <branch-name or task reference> |
Create a traceable Git branch for the current task.
git status, and available task context.<ticket-id>-<short-kebab-summary> when the work has a ticket ID, or <short-kebab-summary> when it does not: lowercase summary of five words or fewer, ticket ID in its own casing, strip anything that is not a letter, digit, or hyphen. If a ticket exists but its ID is not visible, ask when a human is present; unattended, proceed without it and note that in the report.origin/<default>. Branch from anywhere else only when the user explicitly asks to stack.