Code Reviewer
Low RiskAutomated code review and quality checks
Editorial assessment
Where Code Reviewer fits
Code Reviewer is currently positioned as a development skill for engineering teams running repository, CI, and issue workflows. Based on the available metadata, the core job to be done is straightforward: automated code review and quality checks.
The current description adds a practical clue about how the skill behaves in the field: review pull requests, check code quality, suggest improvements, and enforce coding standards. integrates with github, gitlab, and bitbucket. Combined with an npm-based install path, this makes Code Reviewer easier to evaluate than pages that only list a name and external link.
Code Reviewer can usually be trialed quickly, as long as the source and permissions still get reviewed. The current record points to Repository read access and PR comment access as part of the operational surface, which should be reviewed during security and workflow testing.
Best fit
engineering teams running repository, CI, and issue workflows
Install surface
npx skills add code-reviewer
Source signal
Public source link available
Workflow tags
Code review, Quality, and Development
Adoption posture
Install command documented
Risk review
Can usually be trialed quickly, as long as the source and permissions still get reviewed
Priority review
Why this skill deserves a closer look
Code Reviewer earns extra editorial attention because it already sits near the top of the skill library by usage or voting signal. For ClawList readers, that makes it a better candidate for deeper evaluation than a one-line listing or an untested community import.
Best for
Best for engineering teams running repository, CI, and issue workflows. This is the kind of skill worth reviewing when you are standardizing a workflow, not just experimenting in a throwaway session.
Last reviewed
April 3, 2026
Key caveats
Even strong community signals do not replace a source review. Check the install path, maintenance history, and permission surface before wider rollout.
This skill advertises compatibility with OpenClaw >=2026.2.0, so confirm your runtime version before you depend on it.
Compare Code Reviewer against adjacent options before standardizing it, because the highest-voted skill is not always the best fit for your exact repo, team, or automation surface.
Alternatives
Install Command
npx skills add code-reviewerRequires OpenClaw >=2026.2.0
Best-fit workflows
Code Reviewer is best evaluated in development environments where automated code review and quality checks
Shortlist it when your team is actively comparing options for code review, quality, and development workflows
Use a disposable workspace for the first pass so you can confirm the install flow, repository quality, and downstream permissions before broader adoption
About
Review pull requests, check code quality, suggest improvements, and enforce coding standards. Integrates with GitHub, GitLab, and Bitbucket.
Rollout checklist
Review the source repository at https://github.com/openclaw/skill-code-reviewer and confirm the README, maintenance activity, and install notes are still current.
Run `npx skills add code-reviewer` in a disposable environment first so you can confirm package resolution, dependencies, and rollback steps.
Verify whether repository read access and pr comment access matches your security expectations and least-privilege model.
Map Code Reviewer against the rest of your stack in code review, quality, and development workflows so the team knows whether it is a standalone tool or a supporting utility.
Key Features
Automated PR reviews
Code quality scoring
Security vulnerability detection
Style guide enforcement
FAQ
What does Code Reviewer help with?
Code Reviewer is positioned as a development skill. Based on the current summary and tags, it is most relevant for engineering teams running repository, CI, and issue workflows, especially when the workflow requires automated code review and quality checks.
How should I evaluate Code Reviewer before using it in production?
Start by running npx skills add code-reviewer in a disposable environment, then review the source repository, permission surface, and any workflow-specific dependencies before wider rollout.
Why does this page include editorial guidance instead of only the upstream docs?
ClawList is trying to make each skill page more useful than a bare directory listing. That means surfacing practical signals like the install surface, source link, permissions, workflow fit, and rollout considerations in one place.
Who is the best first user for Code Reviewer?
The best first evaluator is usually the operator or engineer already responsible for development workflows, because they can verify whether Code Reviewer matches the current stack, risk tolerance, and maintenance expectations.
Use Cases
Maintain code quality standards
Reduce manual review time
Catch bugs early
Security & Permissions
This skill requires the following permissions:
- Repository read access
- PR comment access
Recommendation: Use the principle of least privilege and regularly review skill behavior.