pr-review

Review GitHub Pull Requests against Phoenix/Elixir code quality standards.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/camino-school/lanttern --skill pr-review-camino-school
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/camino-school/lanttern/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/camino-school/lanttern --skill pr-review-camino-school

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of reviewing GitHub Pull Requests against established code quality standards, ensuring consistency and adherence to project guidelines.

Core Features & Use Cases

  • Automated Code Review: Analyzes PRs for adherence to Phoenix/Elixir patterns and Lanttern-specific quality standards.
  • Contextual Analysis: Gathers PR metadata, syncs local branches, and builds diff context for thorough review.
  • History Awareness: Considers previous review feedback and unresolved threads to provide comprehensive assessments.
  • Use Case: A developer submits a PR. This Skill reviews it, checks for adherence to best practices, and provides a summary of its findings, flagging any potential issues before merging.

Quick Start

Use the pr-review skill to review pull request number 123.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate code reviews for Elixir and Phoenix pull requests on GitHub?

You can automate code reviews for Elixir and Phoenix pull requests by analyzing PR metadata, syncing local branches, and evaluating diffs against defined code quality standards to flag potential issues before merging.

What is the best way to check a GitHub PR against existing code quality standards?

Checking a GitHub PR against code quality standards involves gathering review history and unresolved threads, analyzing the diff context, and assessing adherence to project guidelines for a comprehensive evaluation.

Do I need the gh CLI to review GitHub pull requests against project guidelines?

Yes, you need the gh CLI to fetch PR data and git to sync local branches for comparison. These tools gather the metadata and diff context required to perform the automated review.

How does considering previous review feedback improve automated PR analysis?

Considering previous review feedback and unresolved threads during automated PR analysis ensures the assessment is contextually aware, preventing duplicate comments and verifying that past issues have been resolved.

Can I use automated PR review for frameworks other than Phoenix?

This automated PR review is specifically designed to analyze adherence to Phoenix and Elixir patterns, so using it for other frameworks may result in inaccurate assessments outside its defined quality standards.

Why does my automated GitHub PR review require local branch synchronization?

Local branch synchronization is required to build accurate diff context for the review. Syncing branches via git allows the system to compare changes locally against established quality standards thoroughly.