ss-fix
Fix bugs with regression testing and auto-retry. Triggers on fix/debug/broken/error/not-working intent.
What this skill does
# SpecSwarm Fix Workflow
Provides natural language access to `/ss:fix` command.
## Dynamic Context
Recent changes (potential bug source):
`!git log --oneline -5 2>/dev/null || echo "Not a git repository"`
## When to Invoke
Trigger this skill when the user describes ANY software problem:
- Things not working or broken
- Errors, bugs, or failures
- Features not loading or functioning
- Requests to fix, debug, or resolve issues
- ANY report of unexpected behavior
**Examples:**
- "Please fix that the images don't load"
- "Images don't load"
- "Fix the login bug"
- "The checkout is broken"
- "There's an error when submitting forms"
- "Authentication doesn't work"
- "Payment processing fails"
- "The search isn't working"
## Instructions
**Skill-Based Routing:**
1. **Detect** that user described a software problem
2. **Extract** the problem description from their message
3. **Route based on intent clarity**:
**Clear intent** - Execute directly:
- Clear bug descriptions: "fix the login bug", "images don't load", "checkout is broken"
- Action: Immediately run `/ss:fix "problem description"`
**Ambiguous intent** - Ask for confirmation:
- Less specific: "something's wrong with authentication", "the app isn't working right"
- Action: Use AskUserQuestion tool with two options:
- Option 1 (label: "Run /ss:fix"): Use SpecSwarm's systematic bugfix workflow
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
4. **If user selects Option 2**, process normally without SpecSwarm
5. **After command completes**, STOP - do not continue with ship/merge
## What the Fix Command Does
`/ss:fix` runs complete workflow:
- Creates regression tests to reproduce bug
- Implements the fix
- Verifies fix works
- Re-runs tests to catch new failures
- Auto-retries up to 2 times if needed
Stops after bug is fixed - does NOT merge/ship/deploy.
## Semantic Understanding
This skill should trigger not just on exact keywords, but semantic equivalents:
**Fix equivalents**: fix, repair, resolve, debug, correct, address, handle, patch
**Broken equivalents**: broken, not working, doesn't work, not showing, not appearing, not displaying, not rendering, not loading, failing, crashed
**Issue terms**: bug, error, problem, issue, trouble, failureRelated 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.