debug

Included with Lifetime

$97 forever

Systematic debugging workflow. Use for "debug", "fix bug", "not working", "error", "broken".

Code Review

What this skill does


# Debug Assistant

Systematic debugging workflow with documentation.

## Workflow

### 1. Understand Problem

Ask user:
- Error message (exact text)?
- When does it occur? (always, sometimes, specific action)
- What changed recently?
- Console/network errors?

### 2. Create Debug Session

Write to `.planning/DEBUG-LOG.md`:

```markdown
## Active Session

**Issue**: [description]
**Reported**: [date]
**Severity**: [Critical/High/Medium/Low]

### Error
```
[exact error text]
```

### Steps to Reproduce
1. [step]
2. [step]
3. Error occurs

### Expected vs Actual
- Expected: [what should happen]
- Actual: [what happens]
```

### 3. Investigate

**Checklist:**

```bash
# Build & types
bun run build

# Recent changes
git diff HEAD~5
git log --oneline -10
```

**Common causes by error type:**

| Error | Check |
|-------|-------|
| "undefined" | Null handling, async timing |
| "Module not found" | Import paths, file exists |
| Type mismatch | Type definitions |
| RLS violation | Auth state, policies |
| Hydration | Client-only code in SSR |

**Binary search:**
1. Does it work in simpler case?
2. Does removing X fix it?
3. Does adding X break it?

### 4. Document Findings

Update DEBUG-LOG.md:

```markdown
### Attempt 1: Check RLS
- Theory: User lacks access
- Check: Ran query as user
- Result: Policy missing on budgets
- Conclusion: CONFIRMED
```

### 5. Fix

1. Explain fix to user first
2. Make minimal change
3. Don't refactor while fixing
4. Test immediately

### 6. Verify

```bash
bun run build
# Reproduce original steps - should work
```

```
Fix Verified!
Issue: [description]
Root Cause: [what was wrong]
Fix: [what changed]
Files: src/lib/api.ts:45
```

### 7. Close Session

Update DEBUG-LOG.md:

```markdown
## Solution
**Root Cause**: Missing null check
**Fix**: Added optional chaining
**Files**: src/lib/api.ts
**Lesson**: Add to RULES.md if pattern emerges

**Resolved**: [date]
```

## Rules

1. Don't guess - investigate systematically
2. One change at a time
3. Document everything
4. Verify the fix works
5. Minimal fixes, no refactoring
6. Add to RULES.md if pattern emerges

Files: 1

Size: 2.3 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/potenlab/marketplace-potenlab/tree/main/reference/medium-project/skills/debug

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