Skip to content
TrustedSkillsbeta
Back to all skills

Sentry Pr Code Review

Official
getsentry·vlatest·backend

Automates initial code review checks in pull requests, identifying potential errors and style inconsistencies before human review.

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/sentry-agent-skills --skill sentry-pr-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/sentry-agent-skills at 9f54eb0219.

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

Commit
9f54eb0219
Manifest
skills/sentry-pr-code-review/SKILL.md
Scanned
1 file, 100 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 sentry-pr-code-review skill enables AI agents to analyze and review code changes in pull requests. It identifies potential bugs, security vulnerabilities, performance issues, and style inconsistencies within the modified code. The tool is specifically optimized for backend development workflows.

When to use it

  • Before merging a feature branch into the main codebase to catch errors early
  • As part of an automated CI/CD pipeline to enforce code quality standards
  • To review contributions from external collaborators or junior developers
  • When refactoring large sections of code and needing immediate feedback

Key capabilities

  • Detects common coding mistakes and anti-patterns
  • Highlights security issues such as SQL injection or XSS vulnerabilities
  • Suggests performance optimizations for backend systems
  • Enforces consistent coding style and best practices

Example prompts

  • "Review this pull request for potential bugs and security issues."
  • "Analyze the changes in this PR and suggest improvements for code quality."
  • "Check if this new feature implementation follows our backend development standards."

Tips & gotchas

  • Ensure that the AI agent has access to the full project context, including dependencies and configuration files.
  • While the tool is highly accurate, it should not replace human judgment—always verify critical findings manually.