code-review Skill
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps. Published by anthropics in knowledge-work-plugins.
Decision snapshot
Is this a fit?
Security review, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
22 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is code-review Skill?
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps. Published by anthropics in knowledge-work-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Declared skill metadata
- Source file: engineering/skills/code-review/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use code-review Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/knowledge-work-plugins
- Skill file: engineering/skills/code-review/SKILL.md
What it does
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
Skill instructions
/code-review 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. Usage /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. How It Works ┌─────────────────────────────────────────────────────────────────┐ │ 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
Verified compatibility and discovery
Frequently asked questions
What is code-review?
code-review is a open-source AI agent skill with Copy skill directory. Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks.
Who is code-review best for?
code-review is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install code-review?
Install or run code-review using Copy skill directory. Check code-review for the latest setup command.
Is code-review actively maintained?
code-review may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
