code-review

Identify code quality, security, and maintainability issues in changed code and pull requests.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/AdemKao/ai-cowork --skill code-review-ademkao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/AdemKao/ai-cowork/tree/main/.ai/skills/code-review
Command: npx skills add https://github.com/AdemKao/ai-cowork --skill code-review-ademkao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing code changes for quality, security, and maintainability can be time-consuming and error-prone without a consistent standard.

Core Features & Use Cases

  • Structured Code Review guidance focusing on code quality, security, maintainability, and architectural alignment.
  • PR & Commit Review workflows: assess changes across languages and frameworks, report blockers, improvements, and best practices.
  • Automated Report: Generate a formal review report with sections for findings, blockers, suggestions, and positive notes.

Quick Start

Review the provided diff or PR context and produce a structured assessment focusing on quality, security, and maintainability.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for pull requests?

Automate code review for pull requests by applying a structured checklist to identify code quality, security, and maintainability issues. Generate a formal review report highlighting blockers, improvements, and best practices across various languages and architectures.

What is the best way to check code quality and security in a git diff?

Check code quality and security in a git diff by applying static analysis principles to the changed code. Assess maintainability and architectural alignment to produce a formal report detailing findings, blockers, suggestions, and positive notes.

Can I review code changes across multiple programming languages?

Review code changes across multiple programming languages by applying a consistent structured checklist to the diff or pull request context. Generate a standardized assessment report focusing on quality, security, and maintainability regardless of the framework.

How does a structured pull request review report work?

A structured pull request review report works by organizing automated assessment findings into specific sections for blockers, improvements, suggestions, and positive notes. It enforces a consistent standard for evaluating code quality, security, and architectural alignment.

When do I need a formal code review checklist?

You need a formal code review checklist when evaluating code changes for quality, security, and maintainability becomes time-consuming or error-prone. It ensures consistent assessment across iterative changes, branches, and pull requests, preventing overlooked architectural issues.

What are the limitations of automated static analysis for maintainability?

Automated static analysis for maintainability focuses on identifying issues in changed code and PRs, but requires clear diff context. It reports blockers and improvements based on a structured checklist, yet may not fully grasp complex business logic or architectural nuances.