bug-review
From the author
Hunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.
Install
npx skills add athola/claude-night-market --skill bug-review -a claude-code
Installs to .claude/skills/bug-review/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 85
Security100
Provenance70
Maintenance100
Licence100
Adoption42
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- bug-huntersickn33/agentic-awesome-skillsSystematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.Engineering★ 48.4K
- hunttw93/WazaFinds root cause before any fix. Use when something errors, crashes, regresses, or used to work. Not for code review or new features.Engineering★ 7.4K
- find-bugsgetsentry/skillsFind bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.OfficialSecurity★ 1.1K
- systematic-debuggingcbrock84/headcountFinds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.Engineering★ 2.1K
- diagnosing-bugsOyadotAI/oya-browserThis skill should be used when diagnosing a reported bug, intermittent failure, stuck operation, or performance regression and isolating its cause with reproducible evidence.Other★ 351
- bug-diagnosismohitagw15856/pm-claude-skillsDiagnose a bug systematically instead of guessing — reproduce, isolate, form hypotheses, and test them to root cause. Use when debugging, chasing a defect, an intermittent failure, or 'why is this happening?'. Produces a structured diagnosis: a reliable repro, the narrowed-down location, ranked hypotheses with how to test each, and the root cause + fix once found.Testing★ 1.5K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in