Skip to main content
agentsSource-backedReview first Safety Privacy

Code Reviewer Agent - Agents

Expert code reviewer that provides thorough, constructive feedback on code quality, security, performance, and best practices

by JSONbored·added 2025-09-15·
HarnessClaude Code
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://google.github.io/eng-practices/review/, https://github.com/JSONbored/awesome-claude/blob/main/content/agents/code-reviewer-agent.mdx
Safety notes
Recommendations may include shell commands, package installs, or file edits; review and run any suggested changes yourself instead of applying them unverified.
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.
Author
JSONbored
Claim status
unclaimed
Last verified
2025-09-15

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

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

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Safety notes

  • Recommendations may include shell commands, package installs, or file edits; review and run any suggested changes yourself instead of applying them unverified.

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.

Schema details

Install type
copy
Reading time
3 min
Difficulty score
28
Troubleshooting
Yes
Breaking changes
No
Full copyable content
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 practices

About this resource

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

## 🎯 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 practices

Source citations

Add this badge to your README

Show that Code Reviewer Agent - Agents is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/agents/code-reviewer-agent.svg)](https://heyclau.de/entry/agents/code-reviewer-agent)

How it compares

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 statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
Submitter
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety · Privacy · Safety · Privacy · Safety · Privacy
Brand
Categoryagentscollectionscollectionsrules
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorJSONboredJSONboredJSONboredJSONbored
Added2025-09-152025-10-022025-10-022025-09-16
Platforms
Claude Code
Claude Code
Claude Code
Claude Code
Source repo
Safety notesRecommendations 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 notesGuides 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— missingCode 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
  • Existing codebase to review
  • Understanding of testing frameworks
  • Git repository setup
  • Existing codebase with CI/CD pipeline
  • Understanding of production deployment processes
  • Team buy-in for code quality standards
  • Access to version control system
— none listed
Install
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.