Skip to content
TrustedSkillsbeta
Back to all skills

Code Review

Official
getsentry·vlatest·backend·Apache-2.0

Automates Sentry error code reviews, suggesting fixes and context based on reported issues directly within your IDE.

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 code-review -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.

Scanned
1 file, 97 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

This skill performs automated code reviews, identifying potential bugs, security vulnerabilities, and style inconsistencies within a codebase. It leverages static analysis techniques to provide feedback without requiring manual execution of the code. The goal is to improve code quality and reduce technical debt through proactive identification of issues.

When to use it

  • Before merging pull requests: Automatically review changes before they are integrated into the main branch.
  • During initial development: Identify potential problems early in the development cycle, reducing debugging time later on.
  • For onboarding new developers: Ensure code adheres to established style guides and best practices.
  • To maintain code quality over time: Regularly review existing codebases for regressions or emerging issues.

Key capabilities

  • Static analysis of code
  • Bug detection
  • Security vulnerability identification
  • Style guide enforcement

Example prompts

  • "Review this Python file: my_script.py."
  • "Analyze the JavaScript codebase in /app/js for potential security vulnerabilities."
  • "Check this pull request for adherence to our coding standards."

Tips & gotchas

The skill's effectiveness depends on having a well-defined set of coding standards or style guides. It is best used as part of an automated CI/CD pipeline rather than a manual process.