code-review

Review pull requests using a Sentry-aligned checklist for runtime, performance, security, and design risks.

Updated May 11, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/Commory --skill code-review-iskenkenya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/IsKenKenYa/Commory/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/IsKenKenYa/Commory --skill code-review-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch defects early and improve code quality by providing a structured, Sentry-aligned checklist for reviewing pull requests and code changes.

Core Features & Use Cases

  • Review Checklist for Key Risks: Assess runtime errors, performance pitfalls, unintended side effects, backwards compatibility, and ORM query efficiency.
  • Security and Robustness Focus: Identify injection, XSS, access control gaps, and secrets exposure before they ship.
  • Design, Testing, and Long-Term Impact Guidance: Evaluate architecture alignment, require appropriate functional/integration/e2e coverage, and escalate changes that could have lasting consequences (e.g., DB schema or API contracts).

Quick Start

Use the code-review skill to review a pull request by checking runtime safety, performance hotspots, security issues, test coverage, and whether the design fits the existing architecture.

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 to catch runtime errors and performance pitfalls?

Review pull requests by applying a structured checklist that assesses runtime correctness, performance hotspots, backwards compatibility, and ORM query efficiency to reduce production risk.

What security issues should I check for during a code review?

During a code review, check for injection vulnerabilities, XSS, access control gaps, and secrets exposure. Identifying these security posture issues before shipping helps prevent unintended side effects and robustness flaws in production.

When do I need to escalate code changes for long-term impact?

Escalate code changes that affect long-term impact areas like DB schema or API contracts. Evaluating architecture alignment and ensuring appropriate functional, integration, and e2e test coverage mitigates lasting consequences from these modifications.

Does this code review checklist work for evaluating backwards compatibility?

Yes, the code review checklist works for evaluating backwards compatibility by assessing unintended side effects and ORM query efficiency. It applies Sentry-grade engineering practices to ensure robust design assessment across code changes.

What is the best way to structure a code review for architecture alignment?

The best way to structure a code review is using a checklist covering design assessment, test coverage expectations, and escalation criteria. This ensures architecture alignment and evaluates runtime correctness, performance, and security posture.