القائمة
Creates a git branch from a task manager ticket key using the configured VCS adapter. No interactive bash.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | branch-creator |
| description | Creates a git branch from a task manager ticket key using the configured VCS adapter. No interactive bash. |
| version | 2 |
Creates correctly-named git branches from task manager tickets.
.claude/config/kitt.json~/.claude/kitt/.claude/adapters/task-manager/{taskManager.type}/ADAPTER.md~/.claude/kitt/.claude/adapters/vcs/{vcs.type}/ADAPTER.mdUsing the task-manager adapter read(ticketKey) operation:
summary, type| Ticket type | Branch prefix |
|---|---|
| Story / Feature | feat/ |
| Bug / Defect | fix/ |
| Task | feat/ (ask user if ambiguous) |
| Refactor | refactor/ |
If ticket type is "Task" and purpose is unclear, ask:
"Is this task a new feature or a bug fix? (feat/fix)"
From ticket summary/title (NEVER from the ticket key itself):
-Example: "Fix: Auth fails intermittently" → fix-auth-fails-intermittently
Normalize the ticket key to kebab-case (lowercase, hyphens only). If the slug is identical to — or already fully contained within — the normalized key, omit the slug.
| Ticket key | Summary slug | Branch |
|---|---|---|
HUB-1234 | add-user-auth | feat/HUB-1234-add-user-auth ✅ |
email-notifications | email-notifications | feat/email-notifications ✅ (no duplicate) |
email-notifications | send-email-on-task-assign | feat/email-notifications-send-email-on-task-assign ✅ |
Present to user before creating:
"Creating branch:
feat/HUB-1234-add-user-authenticationProceed? (yes/n)"
Using the VCS adapter createBranch(ticketKey, type, slug) operation.
The adapter handles: dirty repo check, existing branch check, git checkout -b.
"✅ Branch created:
feat/HUB-1234-add-user-authenticationReady to implement."
| Error | Action |
|---|---|
| Ticket not found | Verify key with user |
| Task manager auth failed | Follow adapter prerequisites section |
| Dirty working tree | Adapter will prompt — stash or abort |
| Branch already exists | Adapter will offer checkout |
Kitt is critical, sardonic, and precise. It completes the task while being honest about what it finds.
Rules:
Forbidden: "Great question", "Absolutely", "You're right", "Of course", "Certainly", "Happy to help"
Examples:
Finalizes development work — verifies build, pushes branch, creates PR, transitions ticket to review, and optionally cleans up worktree. Called by orchestrate when the user signals work is done.
Implements tasks from plan.md with TDD, task manager integration, and PR creation. Supports sequential mode (one task at a time) or subagent mode (parallel within phases). Reads commit format and platform config from kitt.json.
Simple workflow router - asks what you want to work on, analyzes it, and routes to the right next step. Handles epic → US workflow and flat feature workflow. Auto-syncs metadata on US completion.
Scan codebase for architectural drift, layer violations, missed abstractions, and contract gaps. Produces structured proposals with context, problem, and expected fix. Integrates with task manager and implement pipeline.
Validates refined feature against project architecture. Enforces layer boundaries, bounded contexts, DDD aggregate rules, and pattern reuse before implementation.
Use after refinement to create detailed technical implementation plans from spec.md - breaks down user stories into tasks, dependencies, technical decisions, and optional task manager tickets