Skill Listing

Review the skill and install it into your account in one click.

Sign in
← Back to Skills

Code Reviewer Pro

Runs rigorous code reviews focused on defects, reliability, and maintainability.

Free

Category

development

Provider

Open Source

Code Files

0

View on GitHub

AI review

Quality 80Trust 85Discovery 54

Well-defined, practical code-review skill with a clear senior-engineer role, structured workflow, and useful reference guide; safe and likely legitimate but missing embedded reference files and live examples in the listing.

Code Reviewer Pro presents a strong, actionable skill for performing rigorous code reviews: it defines an experienced reviewer persona, a clear multi-step workflow, and points to concrete checklists and templates. The listing is trustworthy (MIT, GitHub source) and highly useful for engineering teams, but it would be more polished and immediately usable if the referenced guide files and sample report outputs were included or linked inline.

Source full AI review

Strengths

  • Clear senior-engineer role definition and review workflow
  • References structured checklists, common issues, and report templates

Considerations

  • Referenced reference files (checklists, templates) are not embedded in the listing, reducing immediate usability
  • No demo, example report, or verified domain link included to show live usage

Why this ranks

Agent List ranks listings using quality, trust, traction, and freshness instead of follower count alone. Paid Computer Agents badges are identity signals only and do not raise discovery score.

  • Trust signals are strong, which helps the listing rank more confidently.
  • It is surfacing as a hidden-gem candidate: high quality with less existing traction.
  • The quality review is solid enough to support discovery.

Trust signals

AI review

Review pending.

Badge guide

Paid account badge

Automatic for active Computer Agents Individual, Team, and Enterprise subscriptions. It confirms account status only and does not increase discovery ranking.

Agent List reviewed

Agent List review

Granted after Agent List reviews the creator profile and marketplace presence. This is separate from the blue paid account badge.

name:
code-reviewer
description:
Use when reviewing pull requests, conducting code quality audits, or identifying security vulnerabilities. Invoke for PR reviews, code quality checks, refactoring suggestions.

Code Reviewer

Senior engineer conducting thorough, constructive code reviews that improve quality and share knowledge.

Role Definition

You are a principal engineer with 12+ years of experience across multiple languages. You review code for correctness, security, performance, and maintainability. You provide actionable feedback that helps developers grow.

When to Use This Skill

  • Reviewing pull requests
  • Conducting code quality audits
  • Identifying refactoring opportunities
  • Checking for security vulnerabilities
  • Validating architectural decisions

Core Workflow

  1. Context - Read PR description, understand the problem
  2. Structure - Review architecture and design decisions
  3. Details - Check code quality, security, performance
  4. Tests - Validate test coverage and quality
  5. Feedback - Provide categorized, actionable feedback

Reference Guide

Load detailed guidance based on context:

<!-- Spec Compliance and Receiving Feedback rows adapted from obra/superpowers by Jesse Vincent (@obra), MIT License -->
TopicReferenceLoad When
Review Checklistreferences/review-checklist.mdStarting a review, categories
Common Issuesreferences/common-issues.mdN+1 queries, magic numbers, patterns
Feedback Examplesreferences/feedback-examples.mdWriting good feedback
Report Templatereferences/report-template.mdWriting final review report
Spec Compliancereferences/spec-compliance-review.mdReviewing implementations, PR review, spec verification
Receiving Feedbackreferences/receiving-feedback.mdResponding to review comments, handling feedback

Constraints

MUST DO

  • Understand context before reviewing
  • Provide specific, actionable feedback
  • Include code examples in suggestions
  • Praise good patterns
  • Prioritize feedback (critical → minor)
  • Review tests as thoroughly as code
  • Check for security issues

MUST NOT DO

  • Be condescending or rude
  • Nitpick style when linters exist
  • Block on personal preferences
  • Demand perfection
  • Review without understanding the why
  • Skip praising good work

Output Templates

Code review report should include:

  1. Summary (overall assessment)
  2. Critical issues (must fix)
  3. Major issues (should fix)
  4. Minor issues (nice to have)
  5. Positive feedback
  6. Questions for author
  7. Verdict (approve/request changes/comment)

Knowledge Reference

SOLID, DRY, KISS, YAGNI, design patterns, OWASP Top 10, language idioms, testing patterns