code-reviewer

Review local changes and remote pull requests for code quality standards.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/PHNX3NT/expert-lamp --skill code-reviewer-phnx3nt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/PHNX3NT/expert-lamp/tree/main/.gemini/skills/code-reviewer
Command: npx skills add https://github.com/PHNX3NT/expert-lamp --skill code-reviewer-phnx3nt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh cli, npm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring code correctness, maintainability, and adherence to project standards for both local changes and remote pull requests.

Core Features & Use Cases

  • Automated PR Analysis: Checks out and analyzes remote pull requests against project standards.
  • Local Change Review: Reviews staged and unstaged changes in the local file system.
  • Comprehensive Feedback: Provides structured feedback covering correctness, maintainability, readability, efficiency, security, and testability.
  • Use Case: Submit your pull request for an automated, in-depth review that identifies potential issues before merging.

Quick Start

Review the current local code changes for correctness and adherence to standards.

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 code changes for correctness and maintainability before committing?

To review local code changes for correctness and maintainability, you can analyze staged and unstaged changes in your local file system against multiple quality pillars including readability, efficiency, security, and testability.

Can I run an automated pull request analysis against project standards using gh cli?

Yes, you can run an automated pull request analysis by checking out and reviewing remote pull requests against project standards using git and gh cli to ensure code correctness and adherence before merging.

What aspects of code quality are checked during a pull request review?

During a pull request review, code quality is checked across multiple pillars: correctness, maintainability, readability, efficiency, security, and testability, providing structured feedback on potential issues.

Do I need npm and git installed to review remote pull requests locally?

Yes, you need git and gh cli installed for local and remote pull request operations, and npm is required to run preflight checks before analyzing code against project standards.

What is the best way to identify security and efficiency issues in staged git changes?

The best way to identify security and efficiency issues in staged git changes is to run a comprehensive local change review that analyzes your code against defined quality pillars and project standards.

Are there limitations when analyzing code for testability and adherence to project standards?

Limitations include relying on local git states and requiring gh cli for remote operations; the analysis covers testability and project standards but depends on npm preflight checks succeeding without errors.