code-review

Review Sentry pull requests for security, performance, and test coverage.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Avi977/ace-claude-toolkit --skill code-review-avi977
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Avi977/ace-claude-toolkit/tree/main/skills/sentry-code-review
Command: npx skills add https://github.com/Avi977/ace-claude-toolkit --skill code-review-avi977

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This set of guidelines provides a structured, evidence-based framework for reviewing code in Sentry projects, helping reviewers identify defects, security issues, and maintainability concerns early in PRs.

Core Features & Use Cases

  • Review Checklist: runtime errors, performance regressions, side effects, backward compatibility, ORM query efficiency, and security vulnerabilities.
  • Design Assessment: evaluate component interactions and alignment with project architecture.
  • Test Coverage: ensure functional, integration, and end-to-end tests accompany changes.
  • Feedback & Communication: offer actionable, respectful feedback and documentation improvements.
  • Long-Term Impact: flag API changes, data migrations, and maintainability considerations for future work.

Quick Start

Review a pull request using this guideline to provide structured, actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a pull request for security vulnerabilities and performance regressions?

Review a pull request for security vulnerabilities and performance regressions by applying a structured review checklist that flags runtime errors, ORM query inefficiencies, and backward compatibility issues. This framework provides actionable feedback to identify defects early in PRs.

What is a code review checklist for Sentry projects?

A code review checklist for Sentry projects is an evidence-based framework covering runtime errors, performance regressions, side effects, security vulnerabilities, ORM query efficiency, and test coverage gaps. It helps reviewers provide structured, actionable feedback during pull requests.

Does this code review guideline work for codebases outside of Sentry?

This code review guideline is designed for Sentry projects and codebases that follow Sentry engineering practices. It is most effective when reviewing pull requests in environments adhering to these specific architectural and testing standards.

How do I assess design quality and component interactions during a PR review?

Assess design quality and component interactions during a PR review by evaluating alignment with project architecture. The framework examines long-term maintainability, data migrations, and API changes to ensure sustainable component interactions.

What is the best way to ensure proper test coverage in pull requests?

The best way to ensure proper test coverage in pull requests is to use a review checklist that verifies functional, integration, and end-to-end tests accompany all changes. It flags coverage gaps to maintain long-term code quality.

What are the limitations of using a structured code review checklist?

A structured code review checklist requires strict alignment with Sentry engineering practices to function correctly. It focuses on specific concerns like ORM query efficiency and backward compatibility, meaning it may not generalize fully to codebases with different architectural standards.