Find Bugs

What it does

The source starts with complete changed-file coverage, then traces inputs, queries, authorization, state and external calls. It asks the reviewer to verify surrounding protections and existing tests before concluding that a suspicious pattern is a real problem. The output is findings rather than automatic code changes.

Best for

A focused review of an implementation branch where the reviewer needs a repeatable way to inspect behavioral and security risks.

Tradeoffs and requirements

Its checklist is broad and still depends on codebase knowledge. Seeing a dangerous API does not prove attacker control, while a clean diff can hide a vulnerable existing caller. Access to the complete change and relevant context is essential.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/getsentry/skills/tree/d12f250460ffd961f549dbebf7eeb0cf4afd4c2e/skills/find-bugs --skill find-bugs

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

No configured text patterns matched. Unmatched or concealed behavior can still exist.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

55/100

55

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Establish the base branch and file inventory, read every changed section and map meaningful data flows. Investigate the most plausible problems against callers and framework configuration before drafting feedback.

How to judge the result

For each finding, provide the concrete trigger, location and effect. Record coverage gaps and distinguish verified protections from assumptions; do not turn untested suspicions into claims of exploitability.