Forgent bug-scanner

diff-first-based skill consuming pr_diff to produce review_issues

install
source · Clone the upstream repo
git clone https://github.com/mirandaguillaume/forgent
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/mirandaguillaume/forgent "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.github/skills/bug-scanner" ~/.claude/skills/mirandaguillaume-forgent-bug-scanner && rm -rf "$T"
manifest: .github/skills/bug-scanner/SKILL.md
source content

Bug Scanner

Guardrails

  • timeout: 5min
  • no_nitpicks
  • no_style_issues

When to Use

Use for:

  • always during code review

Especially when:

  • when reviewing complex logic changes

Context

Consumes: pr_diff Produces: review_issues Memory: short-term

Strategy

Approach: diff-first Tools: read_file

Steps

  1. read the PR diff only, no expanded context
  2. scan for obvious bugs like null derefs, off-by-one, logic errors
  3. ignore likely false positives
  4. return issues with severity location

Red Flags

ExcuseReality
Flagging linter/typechecker issuesThese are caught by CI; duplicating them adds noise
Flagging intentional functionality changesChanges related to the PR purpose are likely intentional
Reading beyond the diffShallow scan focuses on changed lines only

Security

  • Filesystem: read-only
  • Network: none