rapid-fix

Automate end-to-end bug fixes with planning, TDD execution, and commit.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/changoo89/claude-pilot --skill rapid-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rapid-fix
Source: https://github.com/changoo89/claude-pilot/tree/main/.claude/skills/rapid-fix
Command: npx skills add https://github.com/changoo89/claude-pilot --skill rapid-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapid bug fixes require planning, execution, testing, and closure; this Skill consolidates them into a streamlined, auto-driven workflow for small changes.

Core Features & Use Cases

  • Auto-generation of a minimal 1-3 SC plan for simple bugs
  • Direct execution via a coder agent with TDD + Ralph Loop
  • One-click closure with Co-Authored-By attribution

Quick Start

Invoke the rapid-fix command with a simple bug description to auto-generate a minimal 1-3 SC plan, run the fix with TDD + Ralph Loop, and commit on success.

Frequently Asked Questions about rapid-fix

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

FAQPage Schema
How do I automate planning and testing for simple bug fixes?

Automating simple bug fixes is achieved by generating a minimal 1-3 system change plan, executing code via TDD, and auto-committing the closure. This streamlined workflow handles scope validation, coder execution, and optional Co-Authored-By attribution.

What is a minimal workflow for closing one-line code validation issues?

A minimal workflow for validation issues auto-generates a targeted plan, applies a test-driven Ralph Loop for execution, and commits the fix. It consolidates planning, coding, testing, and closure into an automated process.

Can I use automated TDD execution for minor changes without complex refactors?

Yes, automated TDD execution targets minor changes like one-line fixes, deliberately avoiding complex refactors or architecture changes. It validates scope to ensure only simple 1-3 system change modifications are processed.

When should I avoid using an automated end-to-end fix workflow?

You should avoid automated end-to-end fix workflows when the task requires complex refactors or architecture changes. This approach is constrained to simple bugs, limiting execution to 1-3 system changes to ensure rapid closure.