1. Habit
  2. Skills
  3. Find Bugs skill
getsentry · 7K installs

Find Bugs skill
Runs by itself, pull request opened.

Find bugs before branches merge.

Install the Find Bugs skill and make it a habit: follow https://gethabit.dev/skills/getsentry/find-bugs.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

7K installs1K starsApache-2.0 licenceSource on GitHub ↗

Find Bugs

by getsentry · 7K installs

The skill

The find bugs skill from Sentry reviews local branch changes for bugs, security holes and quality issues with a full diff read and a security checklist, then reports verified findings.

Only when you ask.

The habit

Find bugs before branches merge.

↻ Runs by itselfpull request opened

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

pull request opened. Runs in GitHub Actions or Claude Code routine.

  • ↻ pull request opened
  • pull_request.opened

02

It checks its work

full coverage, you decide. If a check fails, it tells you.

  • ✓every changed file is listed as fully read
  • ✓every checklist item is marked clean or flagged
  • ✓each finding has file, line and evidence

03

It remembers

findings per branch. The next run reads it first: past findings and which you chose to fix.

loops/branch-bug-hunt-loop/findings.md

One run, step by step.
Then it stops.

Stop ruleStops after one branch per run.

  1. 01

    Get the diff

    Your agent runs git diff against the default branch from gh repo view and reads every changed line.

  2. 02

    Map the surface

    It lists user inputs, queries, auth checks, session state, external calls and crypto.

  3. 03

    Run the checklist

    It checks injection, XSS, auth, IDOR, CSRF, races, sessions, crypto, disclosure, DoS and logic.

  4. 04

    Verify

    It checks if each issue is handled elsewhere or already tested.

  5. 05

    Audit itself

    It lists files read, checklist results and areas it could not verify.

  6. 06

    Report

    It reports findings by severity with a concrete fix, and you pick what to address.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Find Bugs skill helps.

Use it when

  • ✓ You want a review of your branch
  • ✓ You need a security pass on changes
  • ✓ You audit code before merge

Skip it when

  • – You want automatic fixes
  • – You only need style checks

Questions

Find Bugs skill, answered.

Does it fix the bugs?

No. It only reports findings. You decide what to address.

Does it flag style?

No. It skips style and formatting and puts security first.

How do I install the Find Bugs skill?

Copy the prompt at the top into your agent. It installs the skill from getsentry/skills and sets up the habit. Or run npx skills add getsentry/skills --skill find-bugs.

Is the Find Bugs skill free?

Yes. It is published under Apache-2.0. Habit is free too.

Find Bugs. Now as a habit.

Install the Find Bugs skill and make it a habit: follow https://gethabit.dev/skills/getsentry/find-bugs.md

  • Free
  • No account
  • Undo in one line

All getsentry skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by getsentry, published under Apache-2.0. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.