pr-review

Automate pull request reviews against coding conventions via the GitHub API.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill pr-review-edgeapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/pr-review
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill pr-review-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates the tedious process of reviewing pull requests by enforcing strict coding conventions and providing structured, inline feedback directly on GitHub.

Core Features & Use Cases

  • Automated Standards Enforcement: Automatically checks code against defined TypeScript and review standards.
  • Structured Feedback: Posts categorized comments (Critical, Warning, Suggestion) directly to the GitHub PR.
  • Use Case: When a developer submits a new feature branch, this skill can be triggered to perform an initial pass, ensuring all code meets the team's quality bar before a human reviewer even opens the PR.

Quick Start

Use the pr-review skill to analyze the current pull request and post feedback based on the repository standards.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate pull request reviews against coding standards on GitHub?

Automating pull request reviews involves fetching PR metadata and file patches to check code against established TypeScript conventions, then posting structured inline feedback directly via the GitHub API. This skill performs that initial pass to enforce quality bars before human review.

Do I need the gh CLI and jq to automate code review feedback?

Yes, you need the gh CLI and jq installed to automate code review feedback. The skill requires gh to interact with the GitHub API for fetching pull request data and submitting reviews, while jq processes the JSON API responses.

How does automated PR review handle inline feedback on GitHub?

Automated PR review handles inline feedback by categorizing comments into Critical, Warning, and Suggestion levels. It analyzes file patches against project standards and submits this structured feedback directly to the specific lines of code on the GitHub pull request.

Can I use automated code review to enforce TypeScript conventions on new feature branches?

Yes, you can use automated code review to enforce TypeScript conventions on new feature branches. When a developer submits a branch, the skill triggers an initial pass to ensure all code meets defined project standards before a human reviewer opens the PR.

What is the best way to structure automated feedback for pull requests?

The best way to structure automated feedback for pull requests is by categorizing comments into Critical, Warning, and Suggestion tiers. This provides clear actionable feedback on coding convention violations directly on the GitHub PR interface.