reviewer

Review Git branch changes with codex and post inline GitHub PR comments.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/fairy-pitta/claude-dotfiles --skill reviewer-fairy-pitta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/fairy-pitta/claude-dotfiles/tree/main/skills/reviewer
Command: npx skills add https://github.com/fairy-pitta/claude-dotfiles --skill reviewer-fairy-pitta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes in a Pull Request and posting feedback as inline comments directly on the relevant lines of code.

Core Features & Use Cases

  • Automated Code Review: Leverages 'codex review' to analyze code changes against defined checklists for backend and frontend code.
  • Inline Comment Posting: Automatically posts identified issues as inline comments on GitHub Pull Requests.
  • User Approval Gate: Ensures all proposed comments are presented to the user for review and approval before posting.
  • Use Case: After pushing a feature branch, run this skill to get automated, line-specific feedback on your code directly within the PR, streamlining the review cycle.

Quick Start

Use the reviewer skill to analyze the current branch's changes and post inline comments on the associated pull request after your approval.

Frequently Asked Questions about reviewer

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

FAQPage Schema
How do I post automated code review comments on a GitHub pull request?

Automated code review comments on a GitHub pull request are posted by analyzing changed files with 'codex review' and submitting findings as inline comments via the GitHub API. This skill calculates precise diff positions to attach feedback directly to specific lines of code.

Can I review backend and frontend code changes separately within the same pull request?

Backend and frontend code changes within the same pull request can be reviewed separately by executing targeted reviews based on file paths. The skill performs parallelized code reviews on changed files using distinct checklists for each code type.

How does the user approval gate work before posting inline PR comments?

The user approval gate ensures all proposed inline PR comments are presented to the user for review before posting. The skill aggregates findings from the code review and requires manual approval before submitting any comments to GitHub.

Does this automated pull request review tool require any external dependencies?

This automated pull request review tool requires no external dependencies to function. It operates independently using built-in scripts and references to identify PR metadata, execute 'codex review', and post comments through the GitHub API.

What is the best way to get line-specific feedback on a feature branch before merging?

The best way to get line-specific feedback on a feature branch is to run an automated code review that analyzes changes against defined checklists and posts issues as inline comments directly on the associated GitHub pull request.

When should I not use automated inline comments for pull request reviews?

Automated inline comments for pull request reviews should not be used when you need to bypass the user approval gate, as the skill requires manual review of all aggregated findings before posting any feedback to GitHub.