fix

Included with Lifetime

$97 forever

Use when the user reports a bug, says "fix X", "X is broken", "X doesn't work". Bounded-scope, root-cause-first. Adds a regression test before declaring done. Refuses to expand into refactor.

Code Review

What this skill does


# fix

Find the actual cause. Fix it. Add a regression test. Stop.

## Method

1. **Reproduce.** Get the failing case to a deterministic command line. If you can't reproduce, ask for: exact command, env, input, expected vs actual. **Do not guess.**
2. **Memory pass.** `mem_search { query: <error or symptom>, k: 5 }`. Has this been hit before? Was there a prior fix that regressed?
3. **Hypothesis.** State the hypothesis explicitly. Cite evidence (line numbers, log lines, behaviour).
4. **Verify hypothesis** before patching. Add a `console.log`, run, confirm. If the hypothesis is wrong, restate. Don't patch on a hunch.
5. **Smallest fix.** One concept change. Target the root cause, not the symptom. If the root cause is in unrelated code, surface that — do not silently expand scope.
6. **Regression test.** Write a test that fails on the old code and passes on the new. **Required.**
7. **Verify.** Full test suite. Lint. Typecheck.

## Output shape

```
Symptom:    <quoted error or behaviour>
Reproduce:  <exact command>
Cause:      <one paragraph, w/ file:line citation>
Fix:        <minimal diff, applied>
Test:       <path to new regression test>
Adjacent:   <any related code that might also be wrong, NOT fixed in this PR>
```

## Rules

- No fix without reproduction.
- No fix without a regression test (rare exception: pure config change with no logic).
- No "while I was here" cleanup. Adjacent issues go to memory + a follow-up suggestion.
- If hypothesis is wrong, restart from step 3. Don't pile patches.
- Never delete or `@skip` a failing test to make CI green. The test was right.

## Anti-patterns

- Patching the symptom (e.g. catch + ignore the exception that signals the bug)
- "Should be fine now" without re-running the failing case
- Refactoring while fixing (separate concerns)
- Adding defensive null checks everywhere when one specific path was wrong

## When NOT to use

- Adding a new feature — `/siftcoder:add-feature`
- Refactoring with same behaviour — `/siftcoder:refactor`
- Investigation only — `/siftcoder:investigate`

## Subagent dispatch

- `investigator` agent (if installed) for diagnosis
- `Explore` for read-only mapping if the bug area is unfamiliar
- `general-purpose` for the patch + test, with explicit scope file list

Files: 1

Size: 2.4 KB

Complexity: 6/100

Category: Code Review

Source: https://github.com/ialameh/sift-coder/tree/main/skills/coding/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