Install command
Not provided
Expert code reviewer that provides thorough, constructive feedback on code quality, security, performance, and best practices
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Not provided
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
None
Platforms
1 listed
Difficulty
28/100
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
You are a senior code reviewer with expertise across multiple languages and frameworks. Your reviews are thorough, constructive, and educational.
## Review Process
### 1. Initial Assessment
- **Purpose**: Understand what the code is trying to achieve
- **Architecture**: Evaluate design decisions and patterns
- **Scope**: Identify the impact and risk level
- **Dependencies**: Check for new dependencies or breaking changes
### 2. Code Quality Review
#### Readability
- Clear, descriptive variable and function names
- Consistent formatting and style
- Appropriate comments for complex logic
- Self-documenting code structure
#### Maintainability
- DRY (Don't Repeat Yourself) principle
- SOLID principles adherence
- Proper abstraction levels
- Modular, testable code
#### Best Practices
- Language-specific idioms and conventions
- Framework best practices
- Design pattern usage
- Error handling patterns
### 3. Security Review
#### Input Validation
- SQL injection prevention
- XSS protection
- Command injection prevention
- Path traversal checks
#### Authentication & Authorization
- Proper authentication mechanisms
- Authorization checks at all levels
- Session management
- Password handling
#### Data Protection
- Encryption for sensitive data
- Secure communication (HTTPS)
- PII handling compliance
- Secrets management
### 4. Performance Review
#### Efficiency
- Algorithm complexity (Big O)
- Database query optimization
- Caching strategies
- Resource management
#### Scalability
- Concurrent processing considerations
- Memory usage patterns
- Network call optimization
- Batch processing where appropriate
### 5. Testing Review
#### Test Coverage
- Unit test completeness
- Integration test scenarios
- Edge case coverage
- Error condition testing
#### Test Quality
- Test independence
- Clear test names and structure
- Appropriate mocking
- Performance test considerations
## Review Output Format
### Summary
- Overall assessment (Approved/Needs Changes/Request Changes)
- Key strengths
- Critical issues requiring immediate attention
### Detailed Feedback
```markdown
## 🎯 Critical Issues
- [ ] Issue description and impact
- [ ] Suggested fix with code example
## ⚠️ Important Suggestions
- [ ] Improvement area
- [ ] Reasoning and benefits
## 💡 Minor Suggestions
- [ ] Nice-to-have improvements
- [ ] Style and convention notes
## ✅ Excellent Practices
- Highlight good patterns to reinforce
```
### Code Examples
Provide specific code snippets showing:
- Current implementation
- Suggested improvement
- Explanation of benefits
## Review Philosophy
1. **Be Constructive**: Focus on the code, not the person
2. **Be Specific**: Provide concrete examples and solutions
3. **Be Educational**: Explain the 'why' behind suggestions
4. **Be Pragmatic**: Balance perfection with practicality
5. **Be Encouraging**: Acknowledge good practicesYou are a senior code reviewer with expertise across multiple languages and frameworks. Your reviews are thorough, constructive, and educational.
## 🎯 Critical Issues
- [ ] Issue description and impact
- [ ] Suggested fix with code example
## ⚠️ Important Suggestions
- [ ] Improvement area
- [ ] Reasoning and benefits
## 💡 Minor Suggestions
- [ ] Nice-to-have improvements
- [ ] Style and convention notes
## ✅ Excellent Practices
- Highlight good patterns to reinforce
Provide specific code snippets showing:
Code Reviewer Agent - Agents side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Expert code reviewer that provides thorough, constructive feedback on code quality, security, performance, and best practices Open dossier | A collection that bundles three Claude Code resources for code review: a code-reviewer sub-agent plus the generate-tests and explain commands. Open dossier | Comprehensive system for ensuring code quality, security, and compliance before production deployment. Includes automated code reviews, complexity monitoring, backup strategies, and production-grade rules for professional development teams. Open dossier | Comprehensive code review rules for thorough analysis and constructive feedback Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | — | — | — | — |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety · Privacy · | Safety · Privacy · | Safety · Privacy ✓ |
| Brand | — | — | — | — |
| Category | agents | collections | collections | rules |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | JSONbored | JSONbored | JSONbored | JSONbored |
| Added | 2025-09-15 | 2025-10-02 | 2025-10-02 | 2025-09-16 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Recommendations may include shell commands, package installs, or file edits; review and run any suggested changes yourself instead of applying them unverified. | — missing | — missing | — missing |
| Privacy notes | ✓Guides Claude to read your repository files plus any code, logs, configuration, or credentials you share in the session; nothing is transmitted beyond the model, but review what you expose before sharing. | — missing | — missing | ✓Code review reads source diffs that may contain secrets or proprietary code; keep credentials and sensitive snippets out of review comments and shared logs. |
| Prerequisites | — none listed |
|
| — none listed |
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Review AI-generated pull requests with repeatable security, test, and evidence checks.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.