fix

Apply triaged fixes from review output and run tests.

5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rbah31/claude-code-workflow --skill fix-rbah31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/fix
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill fix-rbah31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Fix phase automates post-review remediation by applying triaged, human-approved changes across the codebase, ensuring consistent, auditable follow-through.

Core Features & Use Cases

  • Load triaged findings from the review output and identify items labeled as fixable.
  • Implement minimal, scoped changes across files or, when necessary, switch to plan mode for larger changes.
  • Re-run tests to verify fixes address the issues without introducing new regressions and provide a clear change log.

Quick Start

Execute the fix phase after human triage and instruct the AI to apply the identified fixes from the review output.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I automate post-review code fixes from a triaged review output?

Automate post-review fixes by loading triaged findings labeled as fixable, applying minimal scoped changes across the codebase, and enforcing guardrails. The system reads the review output and lessons file to apply validated changes without introducing regressions.

How do I ensure automated code fixes don't break existing tests during a sprint?

To ensure automated fixes don't break tests, the system re-runs tests after applying changes to verify issues are resolved. It enforces guardrails and generates a detailed change log documenting exactly what was done and why.

What is the best way to apply minimal validated changes across a codebase after triage?

The best way to apply minimal changes is to execute a fix phase after human triage. This process reads triaged review items, implements scoped file edits, or switches to plan mode for larger modifications to ensure safe remediation.

Can I use this fix workflow for larger codebase changes that require planning?

Yes, you can use this workflow for larger changes. When minimal scoped edits are insufficient, the system switches to plan mode to map out broader modifications while still enforcing guardrails and validating fixes.

When should I switch to plan mode during post-review remediation?

You should switch to plan mode during post-review remediation when the triaged fixes require more than minimal, scoped file edits. This ensures larger codebase changes are planned properly before applying validated modifications.

Why do I need a lessons file to apply fixes from a code review?

A lessons file is needed to provide context for applying fixes, ensuring the automated changes align with established project guardrails and historical insights. It helps generate a detailed fix output documenting the reasoning behind each modification.