patch
Create minimal surgical patch plan for targeted fix. Use for small, focused changes rather than full feature implementations.
What this skill does
# Create Focused Patch Plan
Create a minimal, surgical patch plan to address a specific issue.
## Variables
- `review_change_request`: $1 - Description of the issue to fix
- `spec_path`: $2 (optional) - Path to original specification
## Purpose
Create a PATCH - minimal scope, surgical fix, targeted change.
> "This is a PATCH - keep the scope minimal. Only fix what's described in the review_change_request and nothing more."
## Instructions
### 1. Understand the Issue
Parse the review_change_request:
- What exactly is broken?
- What is the expected behavior?
- What evidence exists (screenshots, errors)?
Do NOT expand scope beyond this specific issue.
### 2. Read Original Spec (if provided)
If spec_path is provided, read it for context:
- Original requirements
- How this issue relates to the spec
- What was the intended behavior
### 3. Analyze Current State
```bash
# See current changes
git diff --stat
# Find relevant files
grep -r "related_term" src/
```
### 4. Determine Minimum Fix
Ask: "What is the smallest change that fixes this?"
- Prefer 1-10 line changes
- Avoid refactoring
- Don't fix unrelated issues
### 5. Create Patch Plan
Write to: `specs/patch/patch-{descriptive-name}.md`
## Plan Format
```markdown
# Patch: [Concise patch title]
## Metadata
- Review Change Request: [from input]
- Spec Path: [if provided]
## Issue Summary
**Problem**: [What's broken - specific]
**Solution**: [Minimal fix approach]
## Files to Modify
[Only files that need changes - specific and minimal]
- `path/to/file.ts`: [What change is needed]
## Implementation Steps
IMPORTANT: Execute every step in order, top to bottom.
### Step 1: [Specific action]
[Exact code change needed]
### Step 2: [Specific action]
[Exact code change needed]
## Validation
Execute every command to validate patch is complete:
- [Specific test command]
- [Manual verification step]
## Patch Scope
- **Lines of code to change**: [estimate]
- **Risk level**: [low/medium/high]
- **Testing required**: [minimal/standard/extensive]
```
## Output
Return ONLY the path to the patch plan file created:
```text
specs/patch/patch-fix-button-disabled-state.md
```
## Scope Guidelines
**Keep Minimal:**
- Fix only the reported issue
- Don't refactor surrounding code
- Don't add unrelated improvements
- Don't update documentation
**Risk Assessment:**
| Lines | Risk |
| --- | --- |
| 1-10 | Low |
| 10-50 | Medium |
| 50+ | High - reconsider scope |
## Integration with Workflow
Patches typically follow review:
```text
/review → Identifies blocker issue
↓
/patch → Creates surgical fix plan (THIS COMMAND)
↓
/implement → Executes patch plan
↓
/review → Re-verifies fix
```
Related in Code Review
gstack
IncludedFast 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)
startup-due-diligence
IncludedLegal 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.
interview-master
IncludedThis 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.
fix-issue
IncludedFixes 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.
sf-apex
IncludedGenerates 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.
swift-development
IncludedComprehensive 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.