comet-hotfix

Executes a streamlined open-build-verify-archive workflow for fixing existing behavior bugs.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-hotfix-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-hotfix
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet-hotfix
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-hotfix-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing a small behavior bug should not require the full ceremony of brainstorming, multi-solution design, and heavy planning. This Skill provides a preset fast-track workflow within the Comet/OpenSpec change system for bugs in existing functionality, while still enforcing reproduction evidence, regression tests, root-cause verification, and controlled archiving. ## Core Features & Use Cases - Streamlined change lifecycle: Runs a six-step preset flow (quick open, direct build, root cause check, verification, archive) using comet state and comet guard commands for recoverable, phase-gated state management. - Evidence-first fixing: Requires reproducing the bug with a failing regression test or documented manual evidence before any source edit, then confirms the root cause is eliminated before verification. - Upgrade assessment: Continuously checks qualitative-change signals (new capability, public API, schema change, cross-module work) and file-count tripwires, pausing for an explicit user decision to continue or escalate to the full /comet-classic workflow. - Use Case: A user reports that an API endpoint returns stale cached data. Invoke the hotfix preset to open a change, reproduce the failure with a regression test, apply the fix, verify at the appropriate scale, and archive the change with spec sync if needed. ## Quick Start Invoke /comet-hotfix and describe the existing behavior bug you want fixed so the preset workflow opens a change and drives it through build, verification, and archive.

Frequently Asked Questions about comet-hotfix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a quick bug fix workflow with Comet?▼

Invoke /comet-hotfix with a description of the behavior bug. The preset opens a streamlined change, initializes recoverable state with comet state init, and advances through build, verification, and archive phases automatically.

When should I use hotfix instead of the full classic workflow?▼

Use hotfix only when fixing existing behavior with no new capability, no interface or architecture changes, and predictable scope. If qualitative-change signals like schema changes or new public APIs appear, the workflow pauses so you can choose to upgrade to /comet-classic.

Does the hotfix workflow require a failing test before fixing?▼

Yes. You must reproduce the bug with minimal repeatable steps and, when automatable, add a regression test that fails for the bug before editing source code. Manual failing evidence is recorded only when automation is impossible.

What happens if my bug fix touches more files than expected?▼

Exceeding the file-count hint threshold (for example more than 4 files) triggers a pause where you explicitly choose to continue the hotfix or upgrade to the full workflow. File count alone never forces an automatic upgrade.

Can the hotfix workflow skip verification or archiving?▼

No. Verification through the comet-verify skill is mandatory, and archiving requires verify_result set to pass plus the final archive confirmation from comet-archive. Delta specs, when present, are synced to the main spec during archiving.