patch

Create and manage patches with /hw:patch through a linear repair workflow.

24|3|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill patch-hypoxanthineovo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch
Source: https://github.com/HypoxanthineOvO/Hypo-Workflow/tree/main/skills/patch
Command: npx skills add https://github.com/HypoxanthineOvO/Hypo-Workflow --skill patch-hypoxanthineovo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patch provides a lightweight, persistent track for small fixes that don't justify a full Milestone, enabling long-term traceability and governance across cycles.

Core Features & Use Cases

  • Persistent lightweight patch tracking across cycles
  • /hw:patch command for creating, fixing, and closing patches
  • Enforces a disciplined lifecycle with states like open, pending_acceptance, and closed
  • Supports structured reporting, audit trails, and cross-cycle context

Quick Start

Create a new patch with /hw:patch 'Describe' and follow the linear repair workflow.

Frequently Asked Questions about patch

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

FAQPage Schema
How do I manage small code fixes without opening a full milestone?

Patch management handles small fixes without opening a full milestone by providing a persistent lightweight track. This ensures long-term traceability and governance across project cycles while keeping changes auditable.

What is the patch lifecycle workflow for traceable repairs?

The patch lifecycle enforces a disciplined linear repair workflow with states like open, pending_acceptance, and closed. Worker separation and structured reporting ensure changes remain auditable across cycles.

How do I create and track a patch using the /hw:patch command?

Create a new patch by entering /hw:patch followed by a description. Follow the guided linear repair workflow to progress through patch lifecycles from open to closed, ensuring structured reporting.

When should I use a lightweight patch track instead of a full milestone?

Use a lightweight patch track for small fixes that do not justify a full milestone. It provides persistent tracking and audit trails across cycles without the overhead of full milestone governance.

Does patch management support worker separation for audit trails?

Patch management supports worker separation within its linear repair workflow. This ensures structured reporting and maintains auditable governance across patch lifecycles for small fixes.