Menu
Emergency bug fixes — rapidly diagnose and fix production issues
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Build and deploy features — branch, implement, commit, review, test, deploy, PR/merge
shadcn/ui component patterns including Radix UI primitives, CVA variants, form components with React Hook Form, and Tailwind CSS styling. Use when creating UI components, building forms, implementing design systems, or working with shadcn/ui.
Add critical test coverage — tests ONLY for functionality that could cause production disasters
List all available tools with their signatures and purposes
Analyze Claude Code audit logs — session summaries, metrics, timelines, anomaly detection, and claim verification
Technical debt and refactoring — analyze, refactor, and validate code improvements
| name | team-fix |
| description | Emergency bug fixes — rapidly diagnose and fix production issues |
| argument-hint | <bug description or issue ID> |
| disable-model-invocation | true |
| allowed-tools | Bash(git *), TaskCreate, TaskUpdate, TaskList, TaskGet |
Rapidly diagnose and fix production issues. Speed is the priority — no reviewer step.
Issue to fix: $ARGUMENTS
Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Create a team and spawn teammates:
fix-<issue-slug>Create the following task list with dependencies:
| # | Task | Owner | Blocked By |
|---|---|---|---|
| 1 | Create hotfix branch hotfix/<issue-id> from main | shipper | — |
| 2 | Diagnose root cause and implement minimal fix | full-stack-developer | 1 |
| 3 | Fix data layer issues (if applicable) | database-admin | 1 |
| 4 | Commit fix with message fix: <description> | shipper | 2, 3 |
| 5 | Run focused tests and deploy | shipper | 4 |
| 6 | Update documentation if fix affects docs | documentor | 5 |
| 7 | Merge hotfix to main, tag patch release | shipper | 5, 6 |
Parallelism: Tasks 2 and 3 can run simultaneously if both are needed.
Execute sequentially using the Task tool:
Task(shipper, "Create hotfix branch hotfix/<issue-id> from main")Task(full-stack-developer, "Diagnose and fix: $ARGUMENTS")Task(database-admin, "Fix data issues for: $ARGUMENTS") — only if data-relatedTask(shipper, "Commit fix: fix: <description>")Task(shipper, "Run focused tests on fix, deploy to production")Task(documentor, "Update docs if fix affects documented behavior: $ARGUMENTS")Task(shipper, "Merge hotfix to main, tag patch release")┌─────────┐ ┌──────────────────┐ ┌─────────┐ ┌──────────┐ ┌────────────┐ ┌─────────┐
│ Shipper │────►│ Full Stack Dev │────►│ Shipper │────►│ Shipper │────►│ Documentor │────►│ Shipper │
│ Hotfix │ │ + DB Admin (||) │ │ Commit │ │Quick Test│ │ Update Docs│ │PR/Merge │
│ Branch │ │ Diagnose & Fix │ │ Fix │ │ & Deploy │ └────────────┘ └─────────┘
└─────────┘ └──────────────────┘ └─────────┘ └──────────┘