$ loading_
Review code changes for security, performance, and correctness before merging.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "code-review" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/engineering/skills/code-review/SKILL.md 2. Save it as ~/.claude/skills/code-review/SKILL.md 3. Reload skills and tell me it's ready
Please review this PR's code changes. Focus on security risks, performance issues, potential bugs, edge cases, and missing error handling, then list recommendations by severity: <PR URL>
A structured review with issues, severity levels, explanations, and suggested fixes.
Here is a code diff. Check for SQL injection, command injection, authorization bypass, sensitive data exposure, or unsafe input handling, and provide fix suggestions: <diff>
An itemized security analysis highlighting exploitable risks, affected locations, and remediation steps.
Please review this change and determine whether it introduces N+1 queries, unnecessary loops, cache invalidation issues, or missed null, exception, or concurrency edge cases: <diff or code snippet>
A review focused on performance and correctness, with specific issues and optimization recommendations.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Review code changes with a structured lens on security, performance, correctness, and maintainability.
/code-review <PR URL or file path>
Review the provided code changes: @$1
If no specific file or URL is provided, ask what to review.
┌─────────────────────────────────────────────────────────────────┐
│ CODE REVIEW │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Paste a diff, PR URL, or point to files │
│ ✓ Security audit (OWASP top 10, injection, auth) │
│ ✓ Performance review (N+1, memory leaks, complexity) │
│ ✓ Correctness (edge cases, error handling, race conditions) │
│ ✓ Style (naming, structure, readability) │
│ ✓ Actionable suggestions with code examples │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Source control: Pull PR diff automatically │
│ + Project tracker: Link findings to tickets │
│ + Knowledge base: Check against team coding standards │
└─────────────────────────────────────────────────────────────────┘
## Code Review: [PR title or file]
### Summary
[1-2 sentence overview of the changes and overall quality]
### Critical Issues
| # | File | Line | Issue | Severity |
|---|------|------|-------|----------|
| 1 | [file] | [line] | [description] | 🔴 Critical |
### Suggestions
| # | File | Line | Suggestion | Category |
|---|------|------|------------|----------|
| 1 | [file] | [line] | [description] | Performance |
### What Looks Good
- [Positive observations]
### Verdict
[Approve / Request Changes / Needs Discussion]
If ~~source control is connected:
If ~~project tracker is connected:
If ~~knowledge base is connected:
Review an analysis for methodology, accuracy, bias, and evidence support.
Generate people analytics reports on headcount, attrition, diversity, and org health.
Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Choose the right Zoom surface for a product use case with clear tradeoffs.
Turn an approved brief into social assets, copy, and a staged campaign.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Review code changes for reuse, quality, and efficiency, then fix issues.
Review code deeply across correctness, tests, security, performance, and product quality.
Run multi-model reviews for code changes, PRs, and risky edits.
Fix lint, formatting, and common code issues before passing CI.
Review security risks for auth, inputs, secrets, APIs, and sensitive features.
Review code or branches for correctness, compatibility, architecture, tests, performance, and security.