sentry-code-review

About sentry-code-review

The sentry-code-review skill analyzes and resolves issues that Sentry flags in GitHub pull request review comments. It is used to review or fix problems identified by Sentry in a PR, either for a specific PR number or by finding recent PRs with Sentry feedback.

It understands Sentry's line-specific PR comment format, where each comment carries metadata (author, file, and line) and a body with collapsible sections for the bug description, severity and confidence, a detailed analysis, a suggested fix, and a prompt for an AI agent. Its workflow fetches PR review comments (via the GitHub API or the PR URL), processes only Sentry bot comments while ignoring others, reads the referenced file and line to verify the issue still exists, understands the root cause, implements a precise fix, and produces a structured summary of issues resolved and those needing manual review. It emphasizes verifying before fixing, reading before editing, and reminding the user to run tests.

It is most useful for developers who want to triage and fix Sentry's automated PR review findings efficiently, with targeted, root-cause fixes and a clear report.

FAQ

When should I use this skill?

When asked to review or fix issues that Sentry identified in GitHub pull request comments, for a specific PR or by finding recent PRs with Sentry feedback.

How does it read Sentry's comments?

It parses Sentry's line-specific PR comments, extracting the file, line, bug description, severity, confidence, detailed analysis, suggested fix, and AI-agent prompt.

Does it act on all PR comments?

No. It processes only comments from Sentry (author starting with sentry) and ignores other bots such as cursor.

What is its fix process?

Verify the issue still exists in the current code, understand the root cause, implement a targeted fix (reading the file before editing), and consider edge cases and side effects.

What does it output?

A structured summary listing issues resolved (with severity, confidence, location, and the fix applied) and issues requiring manual review, plus a reminder to run tests.