🔎 Existing issue check
🧭 Problem
Now:
Both "comet-hotfix" and "comet-tweak" use "build_mode: direct", meaning they are executed directly without going through any review process. Although "hotfix" has a "root cause elimination check", it is merely a verification of whether the bug has been fixed, not a code quality review. "Tweak" is even more straightforward, proceeding directly from "open" to "build", then "verify", and finally "archive".
✨ Proposed solution
Suggestion:
After each task in "Step 2. Direct Build" of the hotfix is completed, add a lightweight code review once (dispatch code-reviewer subagent, but use only the code-quality-reviewer template and skip the spec-reviewer). For "tweak", an additional 6th item can be added to the 5 checks of "lightweight verification": dispatch a simplified version of the code review.
🎯 Primary area
Skill workflow
🪐 Workflow phase
Hotfix
🔀 Alternatives considered
No response
🧰 Compatibility notes
No response
🧩 Additional context
No response
🔎 Existing issue check
🧭 Problem
Now:
Both "comet-hotfix" and "comet-tweak" use "build_mode: direct", meaning they are executed directly without going through any review process. Although "hotfix" has a "root cause elimination check", it is merely a verification of whether the bug has been fixed, not a code quality review. "Tweak" is even more straightforward, proceeding directly from "open" to "build", then "verify", and finally "archive".
✨ Proposed solution
Suggestion:
After each task in "Step 2. Direct Build" of the hotfix is completed, add a lightweight code review once (dispatch code-reviewer subagent, but use only the code-quality-reviewer template and skip the spec-reviewer). For "tweak", an additional 6th item can be added to the 5 checks of "lightweight verification": dispatch a simplified version of the code review.
🎯 Primary area
Skill workflow
🪐 Workflow phase
Hotfix
🔀 Alternatives considered
No response
🧰 Compatibility notes
No response
🧩 Additional context
No response