code-review

Structure code reviews with checklists and feedback patterns for pull requests.

Updated Oct 1, 2025
One-click install
npx skills add https://github.com/chmc/listall --skill code-review-chmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/chmc/listall/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/chmc/listall --skill code-review-chmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review can be inconsistent and time-consuming; this guide provides a structured approach to deliver consistent, high-quality feedback.

Core Features & Use Cases

  • Structured review lenses for code changes, architecture decisions, and CI/CD changes.
  • Constructive critique patterns with actionable examples to guide reviewers.
  • Red Team thinking and antipattern awareness to catch edge cases and potential failures.
  • Escalation and safety guidelines to raise critical issues when needed.

Quick Start

Review a PR by applying the checklist and feedback patterns, then document actionable improvements in the PR notes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I improve code review consistency for pull requests across diverse teams?

Improve code review consistency by applying a structured, lens-based checklist to pull requests, ensuring feedback is thorough and uniform across diverse teams and programming languages.

What is the best way to provide constructive feedback during a code review?

The best way to provide constructive feedback is using established critique patterns with actionable examples, guiding reviewers to document specific improvements directly in the PR notes.

Can I use structured code review guidelines for CI/CD pipeline changes and architectural decisions?

Yes, structured code review guidelines apply to CI/CD pipeline changes and architectural decisions, providing specific review lenses to evaluate complex updates beyond standard source code modifications.

How does Red Team thinking apply to catching edge cases in a code review?

Red Team thinking applies to code review by actively hunting for edge cases and potential failures through antipattern awareness, ensuring reviewers catch critical issues before deployment.

When should I escalate critical issues found during a pull request review?

Escalate critical issues during a pull request review by following established safety guidelines, which define exactly when to raise urgent problems to maintain secure software delivery.