Skip to content
TrustedSkillsbeta
Back to all skills

Find Bugs

Official
getsentry·vlatest·backend·Apache-2.0

Find Bugs automatically identifies and reports code defects, boosting software quality and reducing development time by proactively uncovering issues.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add getsentry/skills --skill find-bugs -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

getsentry

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned getsentry/skills at c2f99a5b04.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c2f99a5b04
Manifest
skills/find-bugs/SKILL.md
Scanned
1 file, 76 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The find-bugs skill helps identify potential software defects and vulnerabilities within code. It analyzes source code to detect common programming errors, security flaws, and performance issues. This skill aims to improve code quality by proactively surfacing problems before they become larger issues in production.

When to use it

  • Code Review: Integrate into a code review process to automatically flag potential issues for developers.
  • Pre-Commit Checks: Run the skill as part of pre-commit hooks to prevent problematic code from being merged.
  • Security Audits: Use during security audits to identify vulnerabilities that could be exploited.
  • Refactoring: Employ when refactoring existing codebases to ensure no new bugs are introduced.

Key capabilities

  • Static Code Analysis
  • Bug Detection
  • Vulnerability Identification
  • Performance Issue Detection

Example prompts

  • "Analyze this Python script for potential errors and security vulnerabilities."
  • "Find any memory leaks in this C++ code."
  • "Review this JavaScript function and identify possible performance bottlenecks."

Tips & gotchas

This skill requires access to the source code being analyzed. The accuracy of bug detection depends on the complexity of the codebase and the thoroughness of the analysis configuration.