
Code Review
This codifies Sentry's engineering practices into a structured code review framework. It walks you through their checklist: runtime errors, N+1 queries, breaking changes, security holes, and whether tests actually cover the requirements. The examples are concrete (Django ORM prefetching, React useEffect dependencies, SQL injection patterns). What's useful here is the approval guidance, it explicitly tells you not to block PRs over style preferences and to focus on risk reduction rather than perfection. If you're doing reviews on a Python/Django or TypeScript/React codebase and want a systematic approach beyond gut feel, this gives you one based on what a large engineering team actually uses.
- install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.
- 9
- skills.sh installs
- 457
- GitHub stars
- 33.2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add davila7/claude-code-templates --skill code-review --agent claude-codeInstalls into .claude/skills of the current project.
Files
Sentry Code Review
Follow these guidelines when reviewing code for Sentry projects.
Review Checklist
Identifying Problems
Look for these issues in code changes:
- Runtime errors: Potential exceptions, null pointer issues, out-of-bounds access
- Performance: Unbounded O(n²) operations, N+1 queries, unnecessary allocations
- Side effects: Unintended behavioral changes affecting other components
- Backwards compatibility: Breaking API changes without migration path
- ORM queries: Complex Django ORM with unexpected query performance
- Security vulnerabilities: Injection, XSS, access control gaps, secrets exposure
Design Assessment
- Do component interactions make logical sense?
- Does the change align with existing project architecture?
- Are there conflicts with current requirements or goals?
Test Coverage
Every PR should have appropriate test coverage:
- Functional tests for business logic
- Integration tests for component interactions
- End-to-end tests for critical user paths
Verify tests cover actual requirements and edge cases. Avoid excessive branching or looping in test code.
Long-Term Impact
Sponsors
Details
- Repository
- github.com/davila7/claude-code-templates
- Categories
- Testing & QA, Security, Git & Pull Requests, Code Review & Quality, Debugging, Design & UI/UX
- First seen
- Jun 3, 2026
More from davila7/claude-code-templates
All 618- Computer Use Agents455
- Powershell Windows454
- React Useeffect454
- Backend Patterns452
- Find Bugs447
- Langgraph447
- Agent Md Refactor446
- Autonomous Agent Patterns446
- D3 Viz445
- Manim444
- Marketing Psychology443
- Requirements Clarity442
- Frontend To Backend Requirements441
- Canvas Design439
- Nowait Reasoning Optimizer438
- Code Review Checklist437
- Prompt Caching437
- Commit435
- Vercel Deployment433
- C4 Architecture430
- Information Security Manager Iso27001428
- Mlflow427
- Statsmodels426
- Prompt Library423