code-review

Coordinates manual and automated checks for systematic code review across eight quality dimensions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/coco-de/skills --skill code-review-coco-de
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/coco-de/skills/tree/main/plugins/cc-code-quality/skills/code-review
Command: npx skills add https://github.com/coco-de/skills --skill code-review-coco-de

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the code review process by providing a structured, checklist-based approach across critical quality dimensions, ensuring consistency and thoroughness.

Core Features & Use Cases

  • Comprehensive Checklist: Covers 8 key areas: Architecture, State Management, Security, Performance, Testing, Readability, Internationalization, and Accessibility.
  • Automated Analysis Integration: Guides users on how to leverage existing tools like melos run analyze and melos run test.
  • Use Case: A developer is about to submit a Pull Request. They can use this Skill to self-review their code against best practices, or a senior developer can use it to guide a formal review, identifying potential issues before they become major problems.

Quick Start

Use the code-review skill to review the files in the 'lib/features/auth' directory.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a systematic code review before submitting a pull request?▼

Systematic code review before a pull request uses a structured checklist across architecture, security, performance, and testing to ensure thoroughness and identify potential issues early.

What quality dimensions should a code review checklist cover?▼

A comprehensive code review checklist covers eight key areas: Architecture, State Management, Security, Performance, Testing, Readability, Internationalization, and Accessibility.

Can I integrate automated static analysis and test runners into my code review process?▼

Yes, code review processes can integrate with automated tools like static analyzers and test runners, guiding users to leverage existing commands such as `melos run analyze` and `melos run test`.

Does this code review approach work for reviewing files within a specific project directory?▼

Yes, you can target the code review process to specific directories, such as reviewing files within the 'lib/features/auth' directory to focus the analysis on relevant modules.

What is the best way to check code quality for security and performance issues?▼

The best way to check security and performance is using a structured manual review approach combined with automated tools, validating code against established best practices across multiple dimensions.