skills.rest
prapanch
prapanchCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Review code by evaluating design, functionality, complexity, tests, and style.

Updated Aug 23, 2026
Search Tags:#code review#pull request#software quality#test coverage#security implications#engineering feedback
One-click install
npx skills add https://github.com/prapanch/agent-coda --skill code-review-prapanch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/prapanch/agent-coda/tree/main/app/code-review
Command: npx skills add https://github.com/prapanch/agent-coda --skill code-review-prapanch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review code in a way that improves long-term codebase health by focusing on what truly matters and giving actionable feedback.

Core Features & Use Cases

  • Review the right layer first: evaluate design and functionality before style to avoid wasting time on low-impact issues.
  • Catch correctness, error handling, security, and scalability: prioritize algorithm soundness, security implications, and acceptable performance.
  • Write feedback that moves the change forward: use clear severity labels, one comment per concern, and language that suggests improvements without dictating.
  • Use cases: reviewing PRs and diffs, assessing sub-agent code for ship readiness, and self-reviewing before delivering changes.

Quick Start

Ask an AI reviewer to review the following pull request with emphasis on design correctness, functionality and error handling, security implications, test coverage, and only then style according to the project’s conventions.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request for correctness and safety?▼

Review a pull request for correctness and safety by evaluating design, functionality, complexity, tests, and style in priority order. Focus on algorithm soundness, security implications, and error handling to determine if the code is safe to merge.

What is the best way to write actionable code review feedback?▼

The best way to write actionable code review feedback is to use clear severity labels and address one concern per comment. Provide guidance that suggests improvements without dictating to keep the engineering feedback constructive.

How do I assess agent-produced code for ship readiness?▼

Assess agent-produced code for ship readiness by applying structured code reviews. Evaluate the design and functionality first, catch security implications, verify test coverage, and ensure the change improves overall system health.

Should I review code style or functionality first in a pull request?▼

Review functionality and design first in a pull request before checking style. Evaluating the right layer first avoids wasting time on low-impact issues and prioritizes algorithm soundness, security, and scalability over formatting.

How can I avoid nitpicking out-of-scope issues during code reviews?▼

Avoid nitpicking out-of-scope issues during code reviews by focusing only on the current change. Restrict feedback to actionable concerns with clear severity labels and ignore pre-existing issues that do not affect the immediate pull request.

Related Skills

Explore More Software Engineering Skills→
lee-tolee-to
56

aif-review

Inspect git diffs and PR metadata to identify code defects and quality issues.

Community
Advanced
shhubbhshhubbh
1

land-and-deploy

Merge PRs, wait for CI, deploy to production, and verify health via canary checks.

Community
Advanced
asgarovfasgarovf
23

code-review

Analyze pull requests for security vulnerabilities and SOLID principles.

Community
Advanced
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced