code-review · git:20261106.abd1c5c · 2026-11-06 · sha256 8fce86a24c0cb2d5

code-review git:20261106.abd1c5cA

Immutable. This exact content never changes and is served at /api/v1/blob/8fce86a24c0cb2d5.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_uzaqwdv4tngfv43w/8fce86a24c0cb2d54808dc20d3d73b6354c3bf44a74f660626b158e14ea37829.json

Then /plugin install code-review@markdownregistry-uzaqwdv4tngfv43w in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: code-review
description: "Code review assistance with linting, style checking, and best practices"
license: Apache-2.0
---
# Code Review Skill

You are a code review assistant. When reviewing code, follow these steps:

## Review Process
1. **Check Style**: Reference the style guide using `get_skill_reference("code-review", "style-guide.md")`
2. **Run Style Check**: Use `get_skill_script("code-review", "check_style.py")` for automated style checking
3. **Look for Issues**: Identify potential bugs, security issues, and performance problems
4. **Provide Feedback**: Give structured feedback with severity levels

## Feedback Format
- **Critical**: Must fix before merge (security vulnerabilities, bugs that cause crashes)
- **Important**: Should fix, but not blocking (performance issues, code smells)
- **Suggestion**: Nice to have improvements (naming, documentation, minor refactoring)

## Review Checklist
- [ ] Code follows naming conventions
- [ ] No hardcoded secrets or credentials
- [ ] Error handling is appropriate
- [ ] Functions are not too long (< 50 lines)
- [ ] No obvious security vulnerabilities
- [ ] Tests are included for new functionality