comet-hotfix

Automates bug-fix workflows from build through verify and archive phases.

2.7k|259|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-hotfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-hotfix
Source: https://github.com/rpamis/comet/tree/main/assets/skills/comet-hotfix
Command: npx skills add https://github.com/rpamis/comet --skill comet-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly fix bugs by skipping brainstorming and moving straight to build, verify, and archive to shorten cycle times.

Core Features & Use Cases

  • Deterministic hotfix path across open → build → root cause check → verify → archive for behavior fixes that do not require new capabilities or changes to interfaces.
  • Phase guards and automatic transitions to minimize manual steps and reduce rollout risk.
  • Seamless integration with existing OpenSpec/Superpowers workflows to ensure traceability and archiving.

Quick Start

Load the comet-hotfix skill and follow the guided prompts to initiate a streamlined hotfix.

Frequently Asked Questions about comet-hotfix

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

FAQPage Schema
What is a deterministic hotfix workflow for behavior fixes?

A deterministic hotfix workflow skips brainstorming and jumps directly to build, verify, and archive phases to rapidly fix behavior bugs without requiring new capabilities or architectural changes.

How do I automate rapid bug-fix cycles to shorten rollout time?

Automate rapid bug-fix cycles by using a guided workflow that bypasses initial brainstorming and moves straight through open, build, root-cause check, verify, and archive phases with automatic transitions and phase guards.

Can I use this automated bugfix path for changes involving new capabilities or interfaces?

No, this automated bugfix path applies only to behavior fixes that do not involve new capabilities or architectural changes, ensuring a rapid and deterministic cycle for straightforward corrections.

How does the hotfix workflow integrate with existing OpenSpec and Superpowers tooling?

The hotfix workflow integrates seamlessly with existing OpenSpec and Superpowers workflows, applying phase guards and automatic transitions to ensure traceability and proper archiving throughout the bug-fix process.

What are the limitations of skipping brainstorming for rapid bug fixes?

Skipping brainstorming limits the workflow to behavior fixes only; it cannot handle new capabilities or architectural changes, restricting its use to straightforward corrections that follow a deterministic open to archive path.

What phase guards and task execution rules apply to the comet-hotfix workflow?

The comet-hotfix workflow applies default phase transitions, task execution rules, and guard checks across open, build, root-cause, verify, and archive phases to minimize manual steps and reduce rollout risk.