implementing-as-hotfix

Reproduce a production defect, apply the smallest safe fix, and open a pull request to the planning branch.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill implementing-as-hotfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-as-hotfix
Source: https://github.com/tuvens/phased-development/tree/main/skills/implementing-as-hotfix
Command: npx skills add https://github.com/tuvens/phased-development --skill implementing-as-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides narrow, production-facing fixes on hotfix branches so a single issue can be repaired quickly without expanding into a full sprint.

Core Features & Use Cases

  • Reproduces the defect before changing code, so the fix is grounded in an observed failure.
  • Applies the smallest safe implementation change, then verifies it with targeted tests and quick smoke checks when needed.
  • Prepares the PR for the planning branch and supports the phased delivery chain with status-board updates and escalation when scope or deployment details are unclear.

Quick Start

Use this skill to reproduce the hotfix bug, apply the smallest safe fix, verify it, and prepare the planning-branch pull request summary.

Frequently Asked Questions about implementing-as-hotfix

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

FAQPage Schema
How do I ship a hotfix for a production bug safely?

To ship a hotfix safely, use a dedicated hotfix branch to reproduce the defect, apply the smallest safe change, run targeted regression checks, and open a pull request to the planning branch.

What's the best way to reproduce a defect before applying a hotfix?

Reproducing a defect before a hotfix involves running a one-shot agent task on the hotfix branch to observe the specific failure, ensuring the smallest safe change is grounded in the actual error.

Does this hotfix workflow require the gh CLI to open pull requests?

Yes, the hotfix workflow requires git, Bash, and the gh CLI to manage dedicated hotfix branches, run verification checks, and open the pull request to the planning branch.

How do I handle deployment ambiguity when implementing a hotfix?

When deployment ambiguity or scope expansion appears during a hotfix, trigger a decision-request escalation and update the status-board to support the phased delivery chain.

When should I not use a dedicated hotfix branch for a bug fix?

Avoid using a dedicated hotfix branch for bugs that require more than the smallest safe change, as this workflow is designed for narrow, single-issue production fixes rather than full sprint changes.