comet-hotfix
Use the Classic preset to repair a localized defect. Use when the user explicitly invokes /comet-hotfix, selects hotfix, or resumes workflow: hotfix.
- License 许可
- MIT
- 所属仓库
- rpamis/comet
- 最近更新
- 2026-11-15
- Stars
- ★ 3.3k
- Forks
- 314
01 前言 Front Matter
- name
- comet-hotfix
- description
- Use the Classic preset to repair a localized defect. Use when the user explicitly invokes /comet-hotfix, selects hotfix, or resumes workflow: hotfix.
02 资源文件 2
- 参考文档agents/openai.yaml169 B
- 参考文档reference/compat.md19.8 KB
03 SKILL.md 正文
Comet Preset: Hotfix
Before starting or resuming, read and follow comet-classic/reference/classic-layout.md. All OpenSpec CLI calls must use the adapter, and all paths must use the bound <classic-*> logical roots.
A short defect-repair flow: open → build → root cause check → verify → archive. It skips brainstorming and a full implementation plan, and applies to repairing existing behavior without designing new features.
All applicability conditions must hold:
- Repair an existing feature without adding a feature.
- No interface changes or architectural redesign.
- The scope is predictable. File counts are advisory and do not automatically require escalation; follow Preset scope in the SDK methods reference.
Escalation: If the changes listed in Preset scope arise, the user decides whether to switch to the full /comet-classic workflow.
On first entering a phase, handing off to a new Agent, or recovering context, read and follow Task context and artifact language. Prefer the current continuation or claimed Action's contextRequest; do not fetch it again during uninterrupted work in the same phase.
Personal memory stores reusable user information. Never save task summaries, progress, command output, or test results.
SDK Run path
First read and follow ordinary commands and checks. New and old Runs use platform tools for ordinary commands and submit actual check reports to the original Run. Automatic upgrades do not restore old check executors. Phase preparation, user choices, task completion, and acceptance requirements remain effective.
On first entering the current SDK phase, changing Agent, or recovering context, read Phase entry and recovery and its current phase section. Reuse applicable instructions already in this session. Follow the current phase below; nextAction.kind recovery routing applies only to old responses without a continuation mode.
When starting or resuming, reuse valid agent.continuation / data.nextAction and the bound change, workspace, phase, and Run revision. Route by known data.runtimeFormat. Run comet state next <change-name> --json only for a cold resume, external state change, or missing information. Follow this section for sdk; the SDK methods reference still governs applicability, reproduction and root cause checks, escalation, and file-count authorization. Submit state and evidence through the commands below. For nextAction.kind: reconcile, run comet state check <change-name> <phase> --recover --json to inspect the original Action. Do not repeat implementation, checks, or Archive while its result is unknown.
- For a new change, choose isolation through Workspace selection. Run
comet classic workspace prepare <name> --isolation <selected-isolation> --jsonand enter the returnedprojectRoot. Create the OpenSpec base directories through Entry and artifacts, runcomet state init <name> hotfix --isolation <selected-isolation>, thencomet state select <name>to bind Hook routing. Follow Entry and artifacts to create the concise OpenSpec artifacts. Preview withcomet guard <change-name> open --jsonand retaindata.approvalHash. Present the Open artifacts and scope to the user. After explicit approval, runcomet guard <change-name> open --apply --approval-hash <approvalHash>. Changed artifacts require a fresh preview and approval; do not reuse an old hash. Open finishes only when the Run enters Build. New changes usecomet-state.yaml; historical changes retain their original filename. - When
hotfix.build.executeis pending, resume Build in the same change, workspace, and Run. Do not initialize again or repeat Open. Follow Preset scope to reproduce the defect, preserve failure evidence, complete tasks, and check the root cause. For a material escalation signal, or a file-count limit without valid authorization, first runcomet state propose-escalation <change-name> --reason "<reason>". Present the reason and the effects of continuing hotfix or upgrading to full; retaindata.wait.proposalHash. After the user chooses, runcomet state decide-escalation <change-name> --proposal-hash <proposalHash> --choice <continue|upgrade>.continuestill requires the reference's scope, risk, and ruling conditions.upgradeenters full Design in the same Run and workspace; immediately follow the entry to load comet-design. Resume a pending Wait with its original proposal; do not repropose or choose for the user. - Once all tasks, necessary checks, and reviews are complete and the preset still applies, run
comet state complete-build <change-name> --session <builder-execution-ref> --checks <checks-json-file>to submit actual results. This adds no user decision. Runtime validates tasks, configuration, workspace, and reports before entering Verify. On failure or uncertainty, inspect the original task through the returned current Action without repeating execution. - When the Run enters Verify, Immediately execute: Use the Skill tool to load the comet-verify skill. Skipping this step is prohibited. Its SDK path completes the report, actual checks, and acceptance. When the Run enters Archive, Immediately execute: Use the Skill tool to load the comet-archive skill. Skipping this step is prohibited. Archive and delivery still require current user authorization. Claim completion only when the current successful result shows a completed Run; read
state next --jsonif completion state is missing.
After each advance, use that result's agent.continuation / data.nextAction. Do not repeat next, select, or check while state is valid and complete; read again only on a cold resume, after external state changes, or for missing information. Resolve decision, evidence, or reconcile within the current Run; execute the corresponding step only for action.
Use the actual --session <builder-execution-ref> for SDK Build; do not repeat it when already supplied.
Compat path
The remaining original Runtime steps apply only to runtimeFormat: compat. Read Compat operations and continue its current phase. SDK does not load that reference.
Optional change walkthrough
At Build completion and before presenting Verify results, check the project .comet/config.yaml field change_walkthrough (enabled by default; only explicit false disables it). When enabled, read and execute Change walkthrough, use the shared template to generate or update the same walkthrough.html, and provide an opening link. When disabled, skip extra explanation, detailed instructions and rendering; retain the existing summary. Archive preserves existing pages with the materials and links to their actual archived location; it does not generate missing pages, add confirmation or rerun code checks for page updates.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes