debug-tools
Iterative debugging workflow with confidence scoring, pattern comparison, and strategic log injection. Investigate, fix, verify loop with auto-cleanup of debug logs and escalation to architectural review after 3 failed attempts. Use when diagnosing unexpected behavior, silent errors, intermittent failures, "tests pass but app fails", or "works in dev but not in prod". Triggers: "debug this", "investigate", "trace issue", "add debug logs", "cleanup debug logs", "why is this broken", "why is X not working". Not for known one-line fixes where the user names file and line, runtime error review on deployed services, or PM bug-report triage.
What this skill does
# Debug Tools
Iterative debugging workflow with flexible technique selection and escalation.
## Workflow
```
investigate --> fix --> verify --> done
^_______________________| (max 3 attempts, then escalate)
```
Core loop: investigate, fix, verify. Techniques (log injection, pattern
comparison, focus area analysis) are tools within investigation, not
mandatory phases. Log cleanup happens automatically after verification
succeeds.
## Triggers
- **Debug a bug** ("debug this", "investigate", "trace issue", "fix bug",
"why is X broken") → [investigation.md](references/investigation.md)
- **Add debug logs** ("add debug logs", "inject logs", "trace with logs")
→ [log-injection.md](references/log-injection.md)
- **Cleanup logs** ("remove debug logs", "cleanup logs") →
[log-cleanup.md](references/log-cleanup.md)
- **Pattern lookup** ("debug patterns", "common bugs", "log format") →
[debugging-patterns.md](references/debugging-patterns.md)
Multiple references may load during one debugging session — investigation
often leads to log injection, then back to investigation.
## Guidelines
- Use confidence scoring honestly: ≥70 reports as probable cause, 50-69
suggests logs, <50 stays internal
- Compare broken code against working examples when root cause is unclear
- Always use `[DEBUG]` prefix for injected logs (enables grep + cleanup)
- Apply minimal fix: smallest change that resolves the issue
- Redact sensitive values (passwords, tokens, PII) in injected logs
- Track fix attempts: escalate to architectural review on the 4th
## Anti-Pattern: Confidence Inflation
Reporting a "fix" with confidence below 70 wastes attempts. Inflated
scores hide the real picture: a fix offered at 60 confidence is a guess.
When evidence is missing, drop down — load logs, gather runtime data,
re-rank — instead of pushing a low-confidence fix through.
## Anti-Pattern: Symptom Whack-a-Mole
Fixing the same symptom in multiple places signals an architectural
issue, not a localized bug. When fix N introduces bug N+1, stop. The
4th attempt must escalate to architectural review: re-examine the
abstraction, the missing layer, or the flawed assumption — not retry a
deeper version of the same approach.
## Anti-Pattern: Production Log Residue
Debug logs left after verification become noise in production output and
risk leaking sensitive context. Cleanup is part of the verify phase, not
a polish step. Run `grep '\[DEBUG\]'` after every fix; remaining matches
are bugs in the workflow.
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.