pr-review
Code Review
Review code like a senior engineer - thorough but practical. Focus on things that actually matter. Don't waste time on style nitpicks a linter should catch.
Review Checklist
Use this checklist to guide your review. Need examples of what to look for? Check out references/common-issues.md for code patterns.
Security (Critical)
- Input validation and sanitization
- SQL injection, XSS, command injection risks
- Auth checks in place and correct
- Sensitive data handling (passwords, tokens, PII)
- Dependency vulnerabilities
Bugs & Logic (Critical)
- Null/undefined handling
- Edge cases (empty arrays, null values, boundaries)
- Error handling in place
More from saturate/claude
codebase-audit
Performs comprehensive codebase audit checking architecture, tech debt, security vulnerabilities, test coverage, documentation, dependencies, and maintainability. Use when auditing a project, assessing codebase health, running security scans, checking for vulnerabilities, reviewing code quality, analyzing tech debt, or asked to audit/analyze the entire codebase.
18stats
Query Claude Code usage stats from observability logs. Shows costs, session summaries, tool usage, token consumption, and more. Use when asked about costs, usage, stats, spending, session history, most-used tools, or token usage. Invoked with /stats or when asking questions like "how much have I spent today?
13azure-init
Initialize local dev environment from Azure DevOps by cloning all project repositories. Use when user asks to "initialize Azure project", "clone Azure repos", "setup Azure project locally", or wants to download all repositories from an Azure DevOps project.
4review
Performs comprehensive code reviews checking for bugs, security issues, performance problems, testing gaps, and code quality. Use when reviewing PRs, code changes, or when asked to review code.
1