code-quality-review

Evaluate code reviews across six dimensions with an anti-pattern catalog.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill code-quality-review-i2oland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality-review
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/code-quality-review
Command: npx skills add https://github.com/I2olanD/dotfiles --skill code-quality-review-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework for evaluating code quality during reviews, ensuring consistent, constructive feedback and mentoring across teams.

Core Features & Use Cases

  • Six evaluation dimensions: Correctness, Design, Readability, Security, Performance, and Testability, to guide comprehensive reviews.
  • Anti-pattern catalog and remediation guidance to identify and address common issues.
  • Use Case: During a PR review, apply the framework to prioritize issues, craft actionable feedback, and align on improvements before merging.

Quick Start

  • When reviewing a PR, apply the six dimensions and the anti-pattern catalog to generate a concise, actionable feedback checklist.

Frequently Asked Questions about code-quality-review

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

FAQPage Schema
How do I structure a code review for a pull request?▼

Structure a code review by applying six evaluation dimensions: Correctness, Design, Readability, Security, Performance, and Testability. This framework enforces consistent, actionable feedback and mentoring across teams during pull request assessments.

What should I evaluate during a code review?▼

Evaluate Correctness, Design, Readability, Security, Performance, and Testability during a code review. Using these six dimensions ensures comprehensive quality assurance and helps identify common issues through an anti-pattern catalog.

How do I identify anti-patterns when reviewing code?▼

Identify anti-patterns by referencing a standardized anti-pattern catalog during code reviews. This approach provides specific remediation guidance to address common issues and align on improvements before merging pull requests.

Can I use a standardized code review framework across different programming languages?▼

Yes, you can apply this standardized code review framework across languages and teams. It provides a consistent evaluation structure for ongoing codebase assessments and merge requests regardless of the specific programming language.

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

The best way to provide constructive code review feedback is by following a standardized workflow. This involves prioritizing issues using an anti-pattern catalog and crafting an actionable feedback checklist to align on improvements before merging.