code-review

Analyze code changes against implementation guidelines and detect breaking changes.

93|15|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/nokonoko1203/claude-code-settings --skill code-review-nokonoko1203
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nokonoko1203/claude-code-settings/tree/main/symlinks/codex/skills/code-review
Command: npx skills add https://github.com/nokonoko1203/claude-code-settings --skill code-review-nokonoko1203

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and standardizes the code review process, ensuring code quality, adherence to best practices, and early detection of potential issues.

Core Features & Use Cases

  • Automated Code Analysis: Performs quality checks, identifies unused code, and analyzes comments.
  • Contextual Review: Reviews code based on specific implementation guidelines for frontend or backend.
  • Impact Analysis: Assesses direct and indirect impacts of changes, including potential breaking changes.
  • Use Case: When submitting a Pull Request, use this Skill to perform a thorough review against established guidelines before human review, catching common errors and ensuring consistency.

Quick Start

Initiate a self-review of the current branch against the main branch.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for a pull request before human review?

Automated code review analyzes code changes against predefined implementation guidelines to identify quality issues and comment anomalies. It assesses direct and indirect impacts to detect potential breaking changes, ensuring consistency before human review.

What is impact analysis in code review and how does it detect breaking changes?

Impact analysis in code review evaluates the direct and indirect impacts of code modifications. It systematically traces changes through the codebase to detect potential breaking changes, ensuring adherence to established development workflow best practices.

Can I review code changes by comparing branches instead of using a pull request number?

Yes, contextual code review supports reviewing pull requests by number or by comparing branches directly. This allows flexible analysis of frontend and backend changes against specific implementation guidelines during development.

What's the best way to ensure adherence to frontend and backend best practices during development?

The best way to ensure adherence to best practices is performing contextual code review based on specific implementation guidelines for frontend or backend. This automated analysis identifies unused code and enforces quality standards consistently.

Why does static analysis miss unused code and comment anomalies in my development workflow?

Static analysis may miss unused code and comment anomalies if not configured with comprehensive implementation guidelines. Automated code review performs dedicated quality checks to identify these specific anomalies and ensure development workflow consistency.