code-reviewer

Reviews local git changes and remote GitHub pull requests for correctness and maintainability.

3|1|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/PALabs-v1/AI_friend --skill code-reviewer-palabs-v1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/PALabs-v1/AI_friend/tree/main/.agents/skills/code-reviewer
Command: npx skills add https://github.com/PALabs-v1/AI_friend --skill code-reviewer-palabs-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing code changes consistently is hard: reviewers miss edge cases, skip security checks, or give unstructured feedback. This Skill provides a disciplined review workflow for both local working-tree changes and remote GitHub Pull Requests, producing structured, actionable feedback. ## Core Features & Use Cases - Dual Review Targets: Reviews local staged/unstaged changes via git diff, or checks out remote PRs by number or URL using the GitHub CLI. - Seven-Pillar Analysis: Evaluates correctness, maintainability, readability, efficiency, security, edge cases, and test coverage. - Structured Feedback: Delivers findings grouped as Critical, Improvements, and Nitpicks, ending with a clear Approved or Request Changes recommendation. - Use Case: A teammate asks you to review PR #123. The Skill checks out the PR with gh, runs the project's preflight suite, analyzes the diff, and returns a prioritized review report. ## Quick Start Ask the agent to review PR #123 or to review your current uncommitted changes.

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 GitHub pull request with an AI agent?

Provide the PR number or URL, and the Skill checks out the branch using the GitHub CLI (gh pr checkout), runs the project's preflight suite, reads the PR description and comments, then analyzes the diff and returns structured feedback.

How to review local uncommitted git changes before pushing?

Ask to review your changes without mentioning a PR. The Skill inspects git status and reads diffs from git diff and git diff --staged, then analyzes the modifications across correctness, security, and testability pillars.

What does the code review feedback structure look like?

Feedback includes a summary, findings grouped into Critical (bugs, security issues), Improvements (quality and performance suggestions), and optional Nitpicks, followed by a clear Approved or Request Changes conclusion.

Does the code review run tests automatically?

For remote PRs, the Skill runs the project's npm run preflight verification suite before analysis. For local changes, preflight is optional and only suggested when the changes are substantial.

What are the limitations of automated code review?

The review relies on static diff analysis and the project's preflight checks, so it cannot verify runtime behavior, business intent, or cross-repository impacts. Human judgment is still needed for architectural decisions.