Setting the chapter. One moment.
Skills
Chapter 5 of 28
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality.
1 minute · 227 words · 14 sections
Follow these guidelines when reviewing code for Sentry projects.
Look for these issues in code changes:
Every PR should have appropriate test coverage:
Verify tests cover actual requirements and edge cases. Avoid excessive branching or looping in test code.
Flag for senior engineer review when changes involve:
# Bad: N+1 query
for user in users:
print(user.profile.name) # Separate query per user
# Good: Prefetch related
users = User.objects.prefetch_related('profile')// Bad: Missing dependency in useEffect
useEffect(() => {
fetchData(userId);
}, []); // userId not in deps
// Good: Include all dependencies
useEffect(() => {
fetchData(userId);
}, [userId]);# Bad: SQL injection risk
cursor.execute(f"SELECT * FROM users WHERE id = {user_id}")
# Good: Parameterized query
cursor.execute("SELECT * FROM users WHERE id = %s", [user_id])Install this repository
npx skills add getsentry/skills/plugin marketplace add getsentry/skillsSkills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
main, last pushed 8 August 2026.SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Sentry, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./getsentry/skills.md, and each chapter at its own .md URL.