code-review

Gather pull request context and classify code issues by severity.

1|Updated Jun 10, 2016
One-click install
npx skills add https://github.com/yykamei/dotfiles --skill code-review-yykamei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/yykamei/dotfiles/tree/main/.config/opencode/skills/code-review
Command: npx skills add https://github.com/yykamei/dotfiles --skill code-review-yykamei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow and guidelines for conducting effective code reviews, ensuring code quality, consistency, and maintainability.

Core Features & Use Cases

  • Context Gathering: Provides commands to gather all necessary information for both pull requests and local diffs.
  • Evaluation Criteria: Outlines clear, language-agnostic criteria for evaluating code changes.
  • Issue Classification: Defines severity levels for identified issues (Critical, Warnings, Suggestions).
  • Structured Feedback: Offers a template for clear and actionable review summaries.
  • Use Case: When reviewing a pull request, use this Skill to systematically gather context, evaluate the code against best practices, and provide constructive feedback in a standardized format.

Quick Start

Use the code-review skill to review the attached pull request by gathering context and evaluating the code changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I systematically review a pull request?

To systematically review a pull request, gather context, evaluate code changes against correctness and consistency criteria, classify issues by severity, and provide structured feedback.

What is the best way to evaluate local diffs before committing?

Evaluating local diffs involves gathering context on the changes and assessing code clarity, completeness, and adherence to project conventions to ensure maintainability before finalizing the commit.

How are code review issues classified by severity?

Code review issues are classified into three severity levels: Critical, Warnings, and Suggestions, which helps prioritize necessary fixes over minor improvements and stylistic preferences.

Can I use this workflow for reviewing code in any programming language?

Yes, this workflow outlines clear, language-agnostic criteria for evaluating code correctness, completeness, clarity, and consistency, making it applicable across different programming languages.

Does this code review process require any specific dependencies or tools?

No, this code review process requires no specific dependencies or external tools, allowing development teams to integrate it directly into their existing git workflow and quality assurance practices.