kiwi-hot-fix

Automate Kiwi hot-fix workflows with TDD, review, and SRS sync.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-hot-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiwi-hot-fix
Source: https://github.com/Snoworca/speckiwi/tree/main/.agents/skills/kiwi-hot-fix
Command: npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-hot-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables developers to address urgent Kiwi issues efficiently by automating the hot-fix workflow, ensuring TDD compliance and rigorous review.

Core Features & Use Cases

  • Urgent Bug Fixes: Handles production bugs, GitHub issues, or reported regressions swiftly.
  • TDD Compliance: Requires reproduction of bugs with failing regression tests before applying fixes.
  • Rigorous Review: Ensures that fixes are reviewed thoroughly for quality and safety.
  • SRS Sync: Delegates SRS synchronization after fix and regression success to maintain SpecKiwi governance.
  • Use Case: When an urgent bug is reported in production, use this Skill to create a fix, run regression tests, and synchronize the SRS without bypassing governance.

Quick Start

Use the kiwi-hot-fix skill to initiate a hot fix for an urgent issue by running the command: kiwi-hot-fix --issue-url <ISSUE_URL>.

Frequently Asked Questions about kiwi-hot-fix

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

FAQPage Schema
How do I fix urgent production bugs without bypassing code review and TDD compliance?

To fix urgent production bugs safely, automate your hot-fix workflow to enforce TDD-based regression tests and rigorous code review before deployment. This ensures quick resolution while maintaining strict development governance and quality standards.

What is the best way to synchronize SRS documentation after applying a hot fix?

The best way to synchronize SRS documentation after a hot fix is to delegate SRS synchronization automatically once the fix and regression tests succeed. This maintains SpecKiwi governance without manual documentation updates post-deployment.

Does the TDD hot-fix workflow require writing failing regression tests before applying code fixes?

Yes, the TDD hot-fix workflow requires reproducing bugs with failing regression tests before applying any code fixes. This ensures the urgent issue is accurately captured and prevents regressions from reoccurring in production.

How do I start an automated hot fix for a reported GitHub issue using TDD?

To start an automated hot fix for a GitHub issue, initiate the workflow by passing the issue URL to the hot-fix command. The system then automates TDD reproduction, code review, and SRS synchronization sequentially.

Do I need a Kiwi setup and MCP server access to run automated urgent bug fixes?

Yes, you need an existing Kiwi setup and MCP server access to run automated urgent bug fixes. These environments provide the necessary infrastructure for executing TDD workflows and maintaining SpecKiwi governance during hot fixes.

When should I not use an automated TDD hot-fix workflow for urgent issues?

You should not use an automated TDD hot-fix workflow when your urgent issue cannot be reproduced with regression tests or when your project lacks Kiwi setup and MCP server access required for SpecKiwi governance compliance.