sentry-pr-code-review

Review and fix GitHub PR issues detected by Seer by Sentry code review comments.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/imrishuroy/algopatterns --skill sentry-pr-code-review-imrishuroy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-pr-code-review
Source: https://github.com/imrishuroy/algopatterns/tree/main/.agents/skills/sentry-pr-code-review
Command: npx skills add https://github.com/imrishuroy/algopatterns --skill sentry-pr-code-review-imrishuroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Seer by Sentry leaves automated bug-prediction comments on GitHub pull requests, but triaging, verifying, and fixing each finding manually is tedious. This Skill fetches those comments, parses the structured findings, and guides you through verifying and resolving each issue. ## Core Features & Use Cases - Fetch Seer Comments: Uses the GitHub CLI to retrieve all review comments from the seer-by-sentry[bot] account on a given PR, or scans recent open PRs to find ones with unresolved Seer feedback. - Parse Structured Findings: Extracts bug descriptions, severity and confidence scores, detailed analysis, suggested fixes, and AI-agent prompts from Seer's markdown comment format. - Verify and Fix: Walks through each finding by reading the referenced file and line, confirming the issue still exists, filtering false positives, and applying fixes. - Use Case: A teammate shares a PR URL and asks you to address the Sentry review. You run this Skill to pull all Seer comments, fix three genuine null-check issues, skip one false positive, and produce a summary table of resolved and skipped items. ## Quick Start Review the Sentry Seer comments on pull request number 42 in this repository and fix the confirmed issues.

Frequently Asked Questions about sentry-pr-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find Sentry Seer comments on a GitHub pull request?

Use the GitHub CLI to query the PR review comments API and filter for the seer-by-sentry[bot] user login. The command gh api repos/{owner}/{repo}/pulls/{PR_NUMBER}/comments with a jq filter returns each comment's file, line, and body.

How do I find which open PRs have unresolved Sentry review comments?

List recent open PRs with gh pr list, then loop through each PR number and count comments from seer-by-sentry[bot] via the GitHub API. PRs with a count greater than zero have unresolved Seer feedback.

What is the correct bot name for Seer by Sentry comments?

The bot login is seer-by-sentry[bot], not sentry[bot] or sentry-io[bot]. Filtering by the wrong login returns zero comments even when Seer has reviewed the PR.

Why are no Seer comments appearing on my new pull request?

Seer skips draft PRs and only runs when a PR is marked Ready for Review, when commits are pushed to a ready PR, or when someone comments @sentry review. Also verify the Seer by Sentry GitHub App is installed on the repository.

Should I apply every suggested fix from Seer automatically?

No. Each finding should be verified by reading the file at the referenced line, confirming the issue still exists in current code, and assessing whether it is a real bug or a false positive before applying any fix.