
Bug Prospector Marketplace
- 3 repo stars
- Updated July 22, 2026
- Terryc21/bug-prospector
bug-prospector is a Claude Code skill that analyzes code through seven behavioral lenses so developers can surface assumption bugs before users hit them in production.
About
bug-prospector is a Claude Code marketplace skill that hunts logic and assumption bugs static linters miss. It applies seven forward-looking lenses—assumptions, state machines, boundaries, lifecycle, errors, time, and platform—to produce ranked reports with citations and optional guided fixes. Run it before a release, after a crash report, or with /bug-prospector quick on recent diffs when code looks fine but real-user behavior might break.
- Seven lenses: assumptions, state machines, boundaries, lifecycle, errors, time, platform
- /bug-prospector quick runs three lenses on recent changes
- Writes ranked reports to .agents/research with fix workflows
- Complements linters and sibling bug-echo post-fix scans
Bug Prospector by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
/plugin marketplace add Terryc21/bug-prospectorAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| repo stars | ★ 3 |
|---|---|
| Last updated | July 22, 2026 |
| Repository | Terryc21/bug-prospector ↗ |
What hidden assumption bugs are lurking in code that compiles, passes tests, and looks fine to linters?
Find behavioral bugs—bad assumptions, state gaps, and fragile error paths—in code that already compiles and passes linters.
Who is it for?
Developers shipping user-facing apps—especially Swift/SwiftUI—who want pre-release behavioral audits beyond pattern linters.
Skip if: Teams needing runtime profiling, single-file style linting only, or guaranteed zero false positives from static rules.
What you get
Produces a markdown audit in .agents/research with severity tables, fragile hotspots, and optional fix passes.
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
FAQ
How is this different from SwiftLint or ESLint?
Linters enforce syntax and known patterns; Bug Prospector questions what your code assumes about users, state, time, and platforms.
What is the quickest way to try it?
Install the plugin, then run /Bug Prospector quick to apply three lenses on recent changes.
Does it modify my code automatically?
By default it writes a report; you can opt into guided fix flows that confirm each change before applying.