Menü
Activated when user explicitly invokes skill:hotfix. Emergency fix streamlined channel: mini brainstorming -> fix -> test -> closing-the-loop(mini). Flexible skill.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Activated before any coding begins. Socratic requirements clarification → project type detection → L4 exploration → outline-first design → save to 6-section roadmap. Flexible skill.
Activate after all tasks are complete. Confirm implementation integrity → roadmap recording → cross-project experience extraction → branch cleanup → local git commit. Rigid skill.
Activated after writing-plans completes. Execute TDD (RED→GREEN→REFACTOR) per sub-function → subagent 8-Dimension Review → Sub-function Full Testing → Full-Scenario Integration Testing after all pass. Bug fixes follow the same flow. Rigid skill.
Activate after design is approved. Break work into function-level TDD Triplet tasks → reference roadmap §4 Anti-Duplication → annotate L2/L3 reuse. Reference implementing and closing-the-loop at end of plan. Flexible skill.
任何编码开始前激活。苏格拉底式需求澄清 → 项目类型检测 → L4勘探 → 大纲先行 → 保存6节roadmap。柔性技能。
所有任务完成后激活。确认实现完整性 → roadmap 记录 → 跨项目经验提炼 → 分支收尾 → 本地 git commit。刚性技能。
| name | hotfix |
| description | Activated when user explicitly invokes skill:hotfix. Emergency fix streamlined channel: mini brainstorming -> fix -> test -> closing-the-loop(mini). Flexible skill. |
Only triggered when the user explicitly invokes skill:hotfix. Not auto-detected.
Not an emergency -> use the standard workflow (brainstorming -> writing-plans -> implementing -> closing-the-loop).
skill:hotfix triggered
|
v
Mini Brainstorming (5 minutes)
-> Clarify the bug symptom and impact scope
-> Locate the involved classes/methods (git log recent changes)
-> Fix approach (1-3 sentences)
-> Record in roadmap Section 5
|
v
TDD Fix
-> RED: Write a reproduction test, confirm the bug exists
-> GREEN: Minimal fix, tests turn green
-> REFACTOR: Search for similar bugs (Grep for the same pattern), fix them together
|
v
Quick Review + Testing
-> Subagent review (8 dimensions, focus: regression risk + correctness)
-> Sub-function full testing (4 category scenarios)
|
v
Closing the Loop (mini)
-> git commit (local)
-> Append to roadmap Section 5
-> If new technical knowledge gained -> L2 extraction
| Phase | Standard Workflow | Hotfix |
|---|---|---|
| brainstorming | Full 4 steps | Mini (only clarify bug + locate code) |
| writing-plans | Feature breakdown + anti-duplication | Skipped |
| implementing | Full per-function cycle | Only fix bug + similar pattern search |
| code review | 8 dimensions, full scope | 8 dimensions, focus on regression + correctness |
| sub-function testing | 4 categories, parallel | 4 categories, parallel |
| integration testing | Cross-scenario | Skipped |
| closing-the-loop | Full 5 items | Mini (3 items) |
| Your Thought | The Truth |
|---|---|
| "This bug is urgent, skip testing and fix it directly" | Emergency fixes need testing the most -- fixing the wrong thing turns one minute into one hour. |
| "Hotfix doesn't need a reproduction test, just change it" | Not reproducing first = you don't know the root cause = may fix the wrong place. |