ha-pr-reviewer

Review Home Assistant GitHub pull requests and provide console feedback.

90.2k|38.4k|Updated Sep 17, 2013
One-click install
npx skills add https://github.com/home-assistant/core --skill ha-pr-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ha-pr-reviewer
Source: https://github.com/home-assistant/core/tree/main/.claude/skills/ha-pr-reviewer
Command: npx skills add https://github.com/home-assistant/core --skill ha-pr-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing Home Assistant pull requests manually requires fetching PR details, diffs, and existing comments, then applying project-specific review standards. This Skill automates that workflow so reviewers can focus on code quality.

Core Features & Use Cases

  • PR Data Retrieval: Uses the GitHub CLI to fetch PR metadata, descriptions, and full diffs.
  • Standards-Based Review: Delegates code review to the ha-review skill, passing the correct target branch for accurate diffing.
  • Comment Audit: Runs a parallel subagent to audit existing PR review comments via the ha-pr-comment-audit skill.
  • Use Case: A maintainer wants to review an incoming Home Assistant PR. They invoke this Skill to get a consolidated console review covering code changes and comment history without posting anything to GitHub.

Quick Start

Review the Home Assistant pull request at the provided GitHub URL and output feedback to the console only.

Frequently Asked Questions about ha-pr-reviewer

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

FAQPage Schema
How do I review a GitHub pull request using the command line?

Use the GitHub CLI with `gh pr view` to retrieve PR metadata and `gh pr diff` to inspect code changes. Combine these commands with project-specific review rules to produce structured feedback.

What is the best way to review Home Assistant PRs?

Fetch the PR details and diff with the GitHub CLI, then apply Home Assistant review standards covering code quality, tests, and architecture. Audit existing comments to avoid duplicate feedback.

Does this skill post comments to GitHub automatically?

No. The skill explicitly outputs review feedback only to the console and does not act on GitHub, preventing accidental posting of unfinished reviews.

Why does the review need the target branch explicitly?

Passing the base branch ensures the diff is computed against the correct target. Without it, the review may compare against the wrong branch and miss relevant changes.

When should I use a parallel subagent for PR comment audits?

Run a parallel subagent when you need to inspect existing review comments without blocking the main code review. This separates comment history analysis from active code feedback.