review

Review Git branches and pull requests for convention and code quality compliance.

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/rfhayn/forager --skill review-rfhayn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/rfhayn/forager/tree/main/.claude/skills/review
Command: npx skills add https://github.com/rfhayn/forager --skill review-rfhayn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the review of code changes for consistency with coding conventions, adherence to manifests, and overall code quality, streamlining the pre-PR and PR processes.

Core Features & Use Cases

  • Branch Review: Analyze local branch changes against main.
  • PR Review: Inspect changes in open pull requests.
  • Code Quality Checks: Validate naming conventions, documentation currency, and commit format.
  • Use Case: Before submitting a pull request, you can use this Skill to ensure your code adheres to the project's standards and is ready for merge.

Quick Start

Run /review to check your current branch, or /review <PR#> to check a specific pull request.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for convention compliance before submitting a pull request?

You can automate code review by running the review process against your local branch to validate naming conventions, documentation currency, and commit format before submitting a pull request.

Can I check a specific open pull request for code quality and manifest adherence?

Yes, you can inspect an open pull request for code quality and manifest adherence by passing the specific PR number to the review command to analyze its changes.

What do I need to run automated PR analysis on my local branch?

To run automated PR analysis on your local branch, you need Git and GitHub CLI installed to perform naming convention checks and documentation validation against the main branch.

Does automated code review work for both local branch changes and open pull requests?

Automated code review works for both local branch changes and open pull requests, analyzing convention compliance, manifest adherence, and code quality scans across both targets.

What is the best way to validate naming conventions and documentation currency in my code?

The best way to validate naming conventions and documentation currency is to run an automated code quality scan that checks your changes against established project standards.