code-review

Identify and communicate high-signal issues in code changes with actionable feedback.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/NoSugarCoffee/dotai --skill code-review-nosugarcoffee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/NoSugarCoffee/dotai/tree/main/skills/code-review
Command: npx skills add https://github.com/NoSugarCoffee/dotai --skill code-review-nosugarcoffee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex code changes require targeted analysis to identify high-value issues without overwhelming developers with noise.

Core Features & Use Cases

  • Focused sub-skills (security-review, performance-review, architecture-review, maintainability-review) to isolate findings.
  • Actionable feedback with concrete fixes and rationale for each detected issue.
  • Full-review workflow support: orchestrate multiple sub-skills and produce consolidated findings.

Quick Start

Ask the user to choose a focus area (security, performance, architecture, or maintainability) and confirm the branch to compare against before starting the review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I get actionable feedback on security and performance issues in my pull requests?

Code review identifies high-signal security and performance issues in pull requests, providing precise, actionable feedback with concrete fixes and rationale for each detected problem to improve overall software quality.

Can I isolate architecture findings from maintainability issues during a code review?

Yes, you can isolate architecture findings from maintainability issues using focused sub-skills. This approach separates concerns, ensuring targeted analysis without overwhelming developers with mixed feedback across different review dimensions.

How do I run a full code review workflow across multiple branches?

To run a full code review, select a focus area like security or performance, confirm the target branch to compare against, and the workflow orchestrates multiple sub-skills to produce consolidated, prioritized findings.

What is the best way to reduce noise when reviewing complex code changes?

The best way to reduce noise is applying focused code review techniques that target high-value issues. By isolating specific areas like architecture or maintainability, you receive precise, actionable feedback instead of generic commentary.

Do I need to specify a branch before starting an architecture review?

Yes, you need to specify a branch to compare against before starting an architecture review. Confirming the focus area and target branch ensures the analysis correctly isolates findings and communicates relevant structural issues.

When should I request a dedicated maintainability review instead of a general code review?

Request a dedicated maintainability review when you need targeted analysis on code structure and readability. This isolates maintainability findings from security or performance concerns, delivering focused, actionable feedback without unrelated noise.