fix

Included with Lifetime

$97 forever

Read a review report and apply fixes to the codebase

Code Review

What this skill does

# Fix Review Issues

Read a code review report and apply all necessary fixes. Critical findings are mandatory. Warnings are applied unless disproportionate. Suggestions are skipped.

## Input

`$ARGUMENTS` is the path to a story file.

## Steps

### 1. Find the Review Report

Derive `story-slug` from the story filename. Read `docs/reviews/{story-slug}/02-review.md`.

If the report status is `PASS`, there is nothing to fix. Write a brief summary to `docs/reviews/{story-slug}/03-fix.md` noting no fixes were needed, and stop.

### 2. Learn the Project

Discover the project's test and lint commands by exploring project configuration files. Look at existing source files to understand the code style.

### 3. Parse Findings

Categorise the findings:

- **Critical** — must fix, no exceptions
- **Warnings** — fix unless doing so requires a disproportionate refactor or conflicts with a Critical fix
- **Suggestions** — skip (these are for humans to consider later)

### 4. Apply Fixes

For each Critical finding, then each Warning:

1. Read the referenced file
2. Understand the issue described
3. Apply the fix
4. Move to the next finding

Do not introduce new features or refactor beyond what the findings require.

### 5. Run Tests

Run the project's test command. All tests must still pass after fixes.

If a fix breaks a test, the fix is wrong — revert it and try a different approach. Tests are the source of truth.

### 6. Run Linters

Run the project's lint and type-check commands. Fix any issues introduced by the fixes.

### 7. Write Summary

Write to `docs/reviews/{story-slug}/03-fix.md`:

```markdown
# Phase 3: Fixes Applied

**Story:** {story file path}
**Date:** {ISO date}

## Critical Fixes

- `path/to/file:line` — {what was fixed}

## Warning Fixes

- `path/to/file:line` — {what was fixed}

## Skipped

- {finding reference} — {reason for skipping}

## Test Results

{Final test output confirming all pass}
```

## Rules

- Do NOT modify test files unless a review finding specifically says to.
- Do NOT add features or refactor beyond what findings require.
- Do NOT apply Suggestions — they are informational only.
- If a fix breaks tests, revert and find an alternative approach.

Files: 1

Size: 2.3 KB

Complexity: 4/100

Category: Code Review

Source: https://github.com/psousa50/claude-plugins/tree/main/plugins/develop/skills/fix

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts