skills.rest
whyleonardo
whyleonardoCOMMUNITY
Explore all skills by this author →
Website𝕏@christianlsb0GitHub

reviewing-code

Review code with a structured checklist covering correctness, security, performance, maintainability, testing, and type safety.

Updated Aug 27, 2026
Search Tags:#checklist#quality#review#guidelines#code-review
One-click install
npx skills add https://github.com/whyleonardo/agent-config --skill reviewing-code-whyleonardo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/whyleonardo/agent-config/tree/main/templates/skills/reviewing-code
Command: npx skills add https://github.com/whyleonardo/agent-config --skill reviewing-code-whyleonardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable approach to code reviews, enabling teams to deliver higher-quality, consistent feedback with less effort.

Core Features & Use Cases

  • Constructive Mindset: Emphasizes objective evaluation over personal critique.
  • Checklist Coverage: Covers correctness, security, performance, maintainability, testing, and type safety.
  • Communication Standards: Recommends conventional prefixes (nit:, suggestion:, question:, issue:) to frame feedback clearly.
  • Use Case: A team standardizes PR reviews across multiple languages and projects.

Quick Start

Request a review of a PR by applying the guidelines, starting with the checklist and suggested phrasing.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I standardize code review guidelines across multiple programming languages?▼

To standardize code review guidelines across multiple programming languages, apply a structured checklist covering correctness, security, performance, maintainability, testing, and type safety to ensure consistent, high-quality feedback across all projects.

What are the best communication prefixes for writing constructive code review feedback?▼

The best communication prefixes for writing constructive code review feedback include nit:, suggestion:, question:, and issue:, which help frame feedback objectively and clarify the intent behind each comment for the author.

How does a code review checklist improve software quality and maintainability?▼

A code review checklist improves software quality and maintainability by enforcing a repeatable evaluation process across categories like security, performance, and type safety, reducing overlooked defects and ensuring objective, actionable feedback.

Can I use a structured code review process for any project scale or context?▼

Yes, you can use a structured code review process for any project scale or context, because the checklist applies language-agnostic principles to correctness, testing, and maintainability, enabling consistent reviews across diverse repositories.

What should be included in a pull request review checklist?▼

A pull request review checklist should include categories for correctness, security, performance, maintainability, testing, and type safety, alongside standardized communication prefixes to deliver clear and actionable feedback.

Related Skills

Explore More Software Engineering Skills→
sonteksontek
1

code-review

Evaluate code changes and generate prioritized actionable feedback.

Community
Basic
basmawebinfo-hubbasmawebinfo-hub

Code Reviewer

Review source code and pull requests for correctness, security, and maintainability issues.

Community
Intermediate
jfrometajfrometa

lint-and-validate

Run lint, type checks, and security audits on Node.js and Python projects.

Community
Advanced
josemartinrodriguezmortalonijosemartinrodriguezmortaloni

securing-code

Scan Python code for SQL injection, hardcoded secrets, and command injection.

Community
Advanced