bugmagnet

name	bugmagnet
description	Discover edge cases and test coverage gaps through systematic analysis. Use when analysing test coverage, finding bugs, hunting for edge cases, or when code-reviewer identifies test gaps.

BugMagnet

Systematic test coverage analysis and bug discovery workflow.

Based on gojko/bugmagnet-ai-assistant.

When to Use

• Analysing test coverage for a module
• Finding edge cases and potential bugs
• When code-reviewer identifies test gaps
• Before releasing critical functionality

Workflow Overview

┌─────────────────────────────────────────────────────────────┐
│  🔍 ANALYSE  → Understand code and existing tests          │
│  📊 GAP      → Identify missing coverage                   │
│  ✍️  WRITE    → Implement tests iteratively                │
│  🔬 ADVANCED → Deep edge case exploration                  │
│  📋 SUMMARY  → Document findings and bugs                  │
└─────────────────────────────────────────────────────────────┘

STOP and wait for user confirmation between phases.

---

Phase 1: Initial Analysis (🔍 ANALYSE)

1. Detect language and testing conventions from file extension and project structure
2. Read implementation file — understand public API, parameters, state, dependencies
3. Locate test file — if none exists, ask user about creating one
4. Check coverage tools — run baseline coverage if available
5. Read existing tests — understand current coverage and patterns
6. Check project guidelines — README, CONTRIBUTING for testing conventions
7. Ask user — "Are there additional files I should review?"

STOP — Wait for user input before proceeding.