code-review

Identify and prioritize defects and maintainability issues in code diffs.

Updated Mar 29, 2026

Search Tags:#security #maintainability #diff #code-review #pull-request #tests #quality-assessment

Ready to run

npx skills add https://github.com/ZenkakuHiragana/my-chezmoi-config --skill code-review-zenkakuhiragana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ZenkakuHiragana/my-chezmoi-config/tree/main/dot_config/opencode/skills/code-review
Command: npx skills add https://github.com/ZenkakuHiragana/my-chezmoi-config --skill code-review-zenkakuhiragana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality reviews help identify defects, design problems, and maintainability issues before changes land, reducing risk and improving long-term health of the codebase.

Core Features & Use Cases

Review diffs, patches, or the entire codebase for correctness, design alignment, and edge-case handling.
Evaluate maintainability, test quality, documentation, and consistency with the project's style.
Provide prioritized findings with severity, evidence, impact, and concrete next steps to help teams decide on merging.

Quick Start

Provide the diff or point to the current codebase to begin an advisory review.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review a pull request for code quality and maintainability issues?▼

To review a pull request for code quality, provide the diff to evaluate correctness, design, tests, and security. It analyzes changed lines and surrounding context to deliver prioritized findings with severity, evidence, impact, and next steps.

What is the best way to identify security and design defects before merging a patch?▼

Identifying security and design defects before merging requires an advisory pre-merge check on the patch. This process evaluates correctness, tests, and performance, providing structured findings with severity and impact to help teams decide.

Can I assess test quality and edge-case handling in my current codebase?▼

Yes, you can assess test quality and edge-case handling by pointing to your current codebase. The review evaluates maintainability, documentation, and project style consistency, focusing only on relevant lines and their surrounding context.

Does the code review process provide concrete next steps for resolving defects?▼

Yes, the code review process provides concrete next steps for resolving defects. It delivers structured findings detailing severity, evidence, and impact, ensuring teams understand maintainability issues and edge-case risks before changes land.

How do I check if a code diff aligns with project style and documentation standards?▼

To check if a code diff aligns with project style and documentation standards, submit the patch for review. It evaluates design alignment, consistency, and documentation quality, returning prioritized findings with evidence to reduce merging risks.