bug-hunt-bench
Quantifies which AI models can reliably identify and fix production bugs, reducing uncertainty in delegating code review and remediation tasks to frontier LL…
Bug Hunt Bench: 105 real bugs in two production repos, frontier coding models (GPT-6, Claude, Grok, Gemini, DeepSeek...) find and fix them in their own CLI, graded blind. Live leaderboard + every receipt.
- Ask Claude to identify and fix bugs in real production codebases using the benchmark CLI.
- Generate a report comparing Claude's bug detection performance against other frontier models.
- Find which bug categories Claude struggles with most across the 105 real production bugs.
Quantifies which AI models can reliably identify and fix production bugs, reducing uncertainty in delegating code review and remediation tasks to frontier LLMs. Provides objective evidence for build-vs-buy decisions on AI-assisted debugging.
Engineering leaders evaluating frontier coding models for bug detection and repair workflows in production systems.
https://github.com/phuryn/bug-hunt-bench
By phuryn
How to Get It
claude plugins install phuryn/bug-hunt-bench
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Identify and fix bugs in real production codebases using the benchmark CLI
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 109 GitHub stars; contributors unknown; last commit 0d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 109 GitHub stars; contributors unknown; last commit 0d ago; license no license.