code-reviewer

Generate structured code review feedback with Summary, Must Fix, Should Fix, Consider, and Positive Feedback sections.

3|Updated Jan 29, 2026

Search Tags:#templates #security #maintainability #quality #code-review #pull-request

Ready to run

npx skills add https://github.com/peopleforrester/claude-dotfiles --skill code-reviewer-peopleforrester

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/peopleforrester/claude-dotfiles/tree/main/skills/development/code-reviewer
Command: npx skills add https://github.com/peopleforrester/claude-dotfiles --skill code-reviewer-peopleforrester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are often inconsistently applied and slow to provide actionable feedback. This Skill delivers a systematic, transparent approach to evaluate changes across correctness, security, performance, and maintainability, producing clear guidance for authors and reviewers.

Core Features & Use Cases

Layered Review Process: Evaluate correctness, security, performance, maintainability, and style in a consistent sequence.
Structured Feedback: Produce a formatted report with sections for Summary, Must Fix, Should Fix, Consider, and Positive Feedback.
Use Case: When reviewing a PR or critical code change, paste the diff and receive a ready-to-submit assessment and concrete improvement suggestions.

Quick Start

Provide the PR diff or code snippet and prompt: "Review this change and return a structured feedback document with the sections: Summary, Must Fix, Should Fix, Consider, Positive Feedback."

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I perform a structured code review for a pull request?▼

A structured code review evaluates pull request diffs across correctness, security, performance, and maintainability. You paste the code changes to generate a formatted feedback document with actionable sections like Must Fix, Should Fix, and Positive Feedback.

What should a code review checklist include to ensure maintainability and security?▼

A code review checklist for maintainability and security should assess code correctness, potential vulnerabilities, performance impacts, and style consistency. This systematic approach ensures reviews are transparently applied and produce clear guidance for authors.

How do I format pull request feedback to make it actionable for code authors?▼

Pull request feedback should be formatted into categorized sections: Summary, Must Fix, Should Fix, Consider, and Positive Feedback. This structured document provides concrete improvement suggestions and ready-to-submit guidance for code authors.

Can I use an automated code review process across different programming languages?▼

Yes, automated code review processes can be applied across different programming languages. By providing a layered assessment of code changes, the review mechanism guides evaluations for correctness and security consistently regardless of the language.

What is the best way to speed up providing actionable suggestions during a code review?▼

The best way to speed up actionable suggestions is to use a systematic review process that applies a defined checklist. This approach automates the evaluation of changes and produces a formatted report with concrete improvement templates.

Why are code reviews often inconsistently applied and how can I fix it?▼

Code reviews are inconsistently applied when lacking a systematic, transparent approach. You can fix this by adopting a layered review process that evaluates changes across defined dimensions and outputs a standardized feedback document.