bugmagnet
Lightweight bug discovery and test coverage analysis for a code module. Use when the user asks to find bugs, analyze test coverage, write edge case tests, or do exploratory testing on a file. Triggers on "bugmagnet", "find bugs in", "test coverage gaps", "edge cases for", or "exploratory testing on <file>".
What this skill does
# BugMagnet
Analyze a code module, write comprehensive edge-case tests, and document discovered bugs.
**Attribution:** Adapted from [BugMagnet AI Assistant](https://github.com/gojko/bugmagnet-ai-assistant) by [Gojko Adzic](https://gojko.net) (MIT License).
## Usage
```
/bugmagnet <implementation-file-path>
```
## Workflow
1. Read the implementation file and its existing tests
2. Identify untested edge cases, boundary conditions, and error paths
3. Write tests — run each one immediately after writing
4. When a test reveals a bug, document it as a skipped test (see format below), then explore nearby: bugs cluster together
5. Summarize findings
Do NOT modify the implementation file. Only write tests.
## Bug Documentation Format
When a test reveals unexpected behavior, create a skipped test using the framework's skip mechanism with "- BUG" in the test name:
```
test.skip('normalizeEmail crashes on input without @ - BUG', () => {
/*
* ROOT CAUSE: destructuring email.split("@") fails when no @ present
* CODE LOCATION: src/validator.ts:49
* PROPOSED FIX: guard with if (!email.includes("@")) before split
* EXPECTED: throws or returns input unchanged
* ACTUAL: TypeError: Cannot read properties of undefined
*/
expect(() => normalizeEmail("nodomain")).not.toThrow();
});
```
Every skipped BUG test must include: ROOT CAUSE, CODE LOCATION, PROPOSED FIX, EXPECTED vs ACTUAL.
## Summary Format
After all tests are written, provide:
```
## Test Coverage Summary
**Tests Added:** N total
- Category 1 (X tests)
- Category 2 (Y tests)
**Results:** X passing, Y skipped (bugs)
**Bugs Discovered:**
1. Bug name — file:line
- Root cause: ...
- Proposed 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.