reviewing-code

Review code changes for defects and maintainability concerns.

5|1|Updated Sep 6, 2009
One-click install
npx skills add https://github.com/bnadlerjr/dotfiles --skill reviewing-code-bnadlerjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/bnadlerjr/dotfiles/tree/main/claude/skills/reviewing-code
Command: npx skills add https://github.com/bnadlerjr/dotfiles --skill reviewing-code-bnadlerjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pragmatic code review balances quality with real-world constraints, helping teams catch real problems after code is written or modified, including features, refactors, or PRs.

Core Features & Use Cases

  • Structured, multi-agent reviews that focus on readability, maintainability, and correctness.
  • Guidance on how to synthesize findings into actionable feedback (critical issues, suggestions, and questions).
  • Reusable review blueprint that preserves context and safety while avoiding unnecessary changes.

Quick Start

Run a code review on the latest changes using the reviewing-code methodology and return a structured report.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I perform a pragmatic code review on a pull request?

Perform a pragmatic code review by evaluating pull request changes for readability, maintainability, and correctness to reveal real defects. This methodology synthesizes findings into a structured report containing critical issues, suggestions, and questions for actionable improvement.

What is the best way to structure actionable feedback for code edits?

The best way to structure actionable feedback for code edits is using a clear summary format that separates critical issues from suggestions and questions. This structured workflow preserves context and safety while guiding reviewers toward sustainable design.

How does multi-agent code review work for refactoring changes?

Multi-agent code review works by applying multiple analytical perspectives to refactoring changes, focusing on maintainability and correctness. It balances quality with real-world constraints to catch real problems without suggesting unnecessary changes to the codebase.

Can I use this structured review methodology for feature implementations?

Yes, you can use this structured review methodology for feature implementations, code edits, and refactors. It guides reviewers on readability and correctness, returning a structured report that highlights maintainability concerns and actionable improvements.

What should I avoid when reviewing code for maintainability?

When reviewing code for maintainability, you should avoid suggesting unnecessary changes that alter context and safety. A pragmatic review focuses strictly on revealing real defects and sustainable design improvements rather than forcing stylistic modifications.