bug-hunter

Analyzes source code to detect logic bugs, race conditions, security flaws, and AI slop patterns.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill bug-hunter-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-hunter
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/bug-hunter
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill bug-hunter-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss non-obvious defects like race conditions, silent error swallowing, unsafe type narrowing, and AI-generated low-quality patterns that pass type-checking but fail in production. This Skill performs adversarial static analysis to surface these hidden issues before they cause outages. ## Core Features & Use Cases - Adversarial Static Analysis: Scans files, folders, or entire repositories for 13 bug categories including async races, security flaws, memory leaks, and state corruption. - Structured Severity Model: Every finding is rated by severity, confidence, and blast radius, then delivered in a strict report with an executive summary, findings table, deep dives, and an action plan. - AI Slop Detection: Identifies vague helper names, lazy abstractions, copy-paste patterns, and defensive code without a threat model. - Use Case: Point it at a TypeScript service directory before a release to catch incorrect memoization, improper cache invalidation, and partial failure scenarios that unit tests missed. ## Quick Start Ask the assistant to run a bug-hunter scan on a specific file, folder, or the entire repository and return the prioritized findings report.

Frequently Asked Questions about bug-hunter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find race conditions and hidden bugs in my code?▼

Run a static analysis scan scoped to a file, folder, or repository. The analysis targets async races, temporal coupling, silent error swallowing, and unsafe narrowing, then reports each finding with severity, confidence, and blast radius ratings.

What kinds of bugs does static code analysis detect?▼

It detects logic bugs, async race conditions, type unsoundness, security flaws, performance traps, memory leaks, API misuse, state corruption, error handling gaps, edge cases, maintainability issues, test gaps, and AI-generated slop patterns.

Can I scan a whole repository or just one file?▼

Yes, three scan modes are supported: FILE_SCAN for a single file, FOLDER_SCAN for a directory, and REPO_SCAN for the full repository. If the input is too large, the analysis asks for a chunking strategy and suggests a risk-based scan order.

Does static analysis work on AI-generated code?▼

Yes, it explicitly detects AI slop patterns such as over-commenting, vague helper names, lazy abstractions, copy-paste code, and unnecessary generics. When code is identified as generated, the analysis says so and lowers confidence scores.

What are the limitations of adversarial static analysis?▼

Static analysis cannot execute code, so it may miss runtime-only behaviors and environment-specific failures. Very large inputs require chunking, and findings on generated code carry lower confidence since intent is harder to infer.