code-reviewer

Analyze local changes and remote PRs to produce structured code review reports.

420|65|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/CoWork-OS/CoWork-OS --skill code-reviewer-cowork-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/CoWork-OS/CoWork-OS/tree/main/resources/skills/code-reviewer
Command: npx skills add https://github.com/CoWork-OS/CoWork-OS --skill code-reviewer-cowork-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers review code efficiently by consolidating local changes and PR context into structured feedback, reducing review cycles and improving code quality.

Core Features & Use Cases

  • Review local changes (staged/unstaged) and PRs by ID or URL with guided analysis.
  • Provide targeted feedback on correctness, maintainability, readability, and security.
  • Use Case: A developer submits a PR; the agent analyzes diffs and PR descriptions to surface issues and suggested improvements.

Quick Start

Review the current local changes or a target PR by ID or URL and produce a structured code-review summary.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review local Git changes before pushing a commit?

To review local Git changes, analyze staged or unstaged diffs to produce structured feedback. This evaluates correctness, maintainability, readability, and security to highlight critical issues and suggested improvements.

Can I analyze a pull request by URL or ID?

Yes, you can analyze remote pull requests by ID or URL. It optionally integrates with gh CLI to fetch PR context and diffs, producing a structured review report with targeted feedback and edge-case considerations.

Does the code review work across different programming languages?

Yes, code review works across repositories and multiple programming languages. It evaluates code changes for correctness, maintainability, readability, efficiency, and security regardless of the specific language or framework used.

What is the best way to automate code review for a pull request?

Automate pull request reviews by fetching PR diffs and descriptions to surface issues and suggested improvements. This targets correctness and security while producing a structured feedback report to reduce manual review cycles and improve code quality.

Do I need gh CLI installed to review pull requests?

gh CLI is not strictly required but is optionally integrated to fetch remote pull requests and run preflight checks. Without it, you can still analyze local staged or unstaged code changes to produce structured feedback.

What specific code quality issues does a diff analysis cover?

Diff analysis covers correctness, maintainability, readability, efficiency, and security. It highlights critical issues, suggested improvements, and edge-case considerations within a structured feedback report for your code changes.