code-reviewer

Reviews local changes and remote PRs with GitHub CLI checkout and structured feedback.

12|7|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/allofmeng/streamline_project --skill code-reviewer-allofmeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/allofmeng/streamline_project/tree/main/.agents/skills/code-reviewer
Command: npx skills add https://github.com/allofmeng/streamline_project --skill code-reviewer-allofmeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers perform fast, rigorous code reviews across local worktrees and remote pull requests, ensuring quality, consistency, and alignment with project standards.

Core Features & Use Cases

  • Determine review targets for both local changes and remote PRs, with guidance on checkout and context.
  • Prepare for review by inspecting diffs, running preflight checks, and reading PR discussions to understand goals.
  • Provide structured feedback across key pillars: correctness, maintainability, readability, efficiency, security, edge cases, and testability, and deliver a final decision.

Quick Start

Identify the review target and follow the guided workflow to produce a thorough review.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review a remote pull request using a URL?

To review a remote pull request, you provide the URL or PR number. The skill checks out the PR with the GitHub CLI, runs preflight checks, reads the PR description and comments, and delivers structured feedback.

Can I review local git changes before pushing to a remote repository?

Yes, you can review local git changes. The skill examines git status and diffs to understand modifications, then provides structured feedback on correctness, maintainability, readability, efficiency, security, edge cases, and testability.

What is the best way to organize feedback during a code review?

The best way to organize code review feedback is by categorizing findings into critical issues, improvements, and nitpicks. This structured approach ensures clarity and concludes with an explicit Approved or Request Changes decision.

Does the code review process require running preflight checks?

Yes, running preflight checks is required for remote pull requests. The skill executes the project's preflight checks after checking out the PR to ensure alignment with project standards before delivering the review feedback.

How do I perform a thorough code review on a local worktree?

To perform a thorough code review on a local worktree, the skill inspects git diffs and status to understand modifications. It then evaluates the changes across key pillars like correctness and maintainability to deliver a final decision.

What should a rigorous code review evaluate for maintainability?

A rigorous code review for maintainability evaluates readability, efficiency, security, edge cases, and testability. The skill inspects diffs and PR discussions to ensure modifications align with project quality and consistency standards.