comet-hotfix

Automate minor bug fix lifecycle with Comet state management and verification.

6|Updated May 25, 2026
One-click install
npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-hotfix-zhentingwu-wzt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-hotfix
Source: https://github.com/zhentingWu-wzt/wgenty-code/tree/main/.wgenty-code/skills/comet-hotfix
Command: npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-hotfix-zhentingwu-wzt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines the bug-fixing process by providing a structured, high-speed path that eliminates unnecessary brainstorming and planning for minor, well-defined issues.

Core Features & Use Cases

  • Preset Workflow: Automates the transition from opening a change to building, verifying, and archiving the fix.
  • Safety Guardrails: Includes a two-stage guardian review and automatic escalation to full workflows if architectural changes are required.
  • Use Case: Quickly resolve a production bug where the root cause is known and the fix is limited to one or two files, ensuring all tests pass and the change is properly archived.

Quick Start

Invoke the comet-hotfix skill to initiate a rapid bug-fix workflow for the current issue.

Frequently Asked Questions about comet-hotfix

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

FAQPage Schema
How do I automate a minor bug-fix workflow from code modification to verification?

An automated bug-fix workflow handles initialization, code modification, verification, and archival for localized code repairs. It bypasses unnecessary planning for well-defined issues while maintaining system integrity through state management and guardrails.

When should I use a rapid hotfix workflow instead of a full development cycle?

Use a rapid hotfix workflow for minor, well-defined production bugs where the root cause is known and fixes span one or two files. It bypasses brainstorming and planning needed for complex architectural changes.

What safety guardrails are included in an automated code repair process?

An automated code repair process includes a two-stage guardian review and automatic escalation to full workflows if architectural changes are detected. It requires integration with state management and verification tools to ensure system integrity.

Can I use an automated bug-fix workflow for refactoring that requires architectural changes?

No, an automated bug-fix workflow is restricted to localized code repairs that do not require architectural changes or complex design documentation. If architectural modifications are detected, the system automatically escalates to a full workflow.

What is the process to archive a localized code fix after tests pass?

Archiving a localized code fix is the final automated step in the bug-fix lifecycle. After the modification is built and all verification tests pass, the workflow automatically archives the change to ensure proper documentation and state closure.