comet-github-pr-review

Reviews GitHub pull requests with evidence-based analysis of diffs, CI status, and merge blockers.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-github-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-github-pr-review
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-github-pr-review
Command: npx skills add https://github.com/rpamis/comet --skill comet-github-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing community pull requests requires checking the latest diff, linked issues, review thread status, mergeability, and CI results, and it is easy to draw conclusions from stale comments or outdated bot output. This Skill enforces a read-only, evidence-first review process so conclusions are always based on the current PR head and base.

Core Features & Use Cases

  • Current-State Refresh: Fetches PR metadata, full diff, commits, comments, and review threads, distinguishing resolved or outdated threads from still-valid concerns.
  • Evidence-Based Implementation Review: Traces real production call paths, compares the implementation against linked issues or specs, and reproduces reachable failure paths before reporting bugs.
  • Merge-Blocking Focus: Reports only must-fix issues affecting correctness, data integrity, security, or mergeability, each with severity, file/line evidence, and a minimal fix direction.
  • Use Case: A maintainer asks whether a community PR is ready to merge; the Skill verifies the head SHA, checks CI status (delegating failures to CI triage), confirms review threads are resolved, and concludes with a clear verdict such as "no must-fix items" or "merge/CI issues must be resolved first".

Quick Start

Use the comet-github-pr-review skill to review pull request number 123 in the comet repository and tell me whether it has any must-fix issues.

Frequently Asked Questions about comet-github-pr-review

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

FAQPage Schema
How do I review a GitHub pull request for merge blockers?

Fetch the current PR metadata, full diff, commits, and review threads, then verify each claimed behavior against real production call paths. Report only issues affecting correctness, security, or mergeability, each with severity, file/line evidence, and a minimal fix direction.

How to check if PR review comments are still valid?

Compare each review thread against the current head SHA to confirm whether it is resolved or outdated. Do not treat all visible comments as still valid, and verify whether the current head already fixes the reported problem.

Does passing CI mean a pull request is mergeable?

No. Passing checks only cover the tested head commit; the head may be behind the base branch or have current merge conflicts. Always confirm mergeable state and that checks correspond to the exact current head SHA.

Can this skill post review comments or fix PR issues automatically?

It is read-only by default and never posts comments without explicit user request. When a fix is requested, confirmed scope is handed to a dedicated issue-fix workflow rather than applying unverified bot suggestions.

Should I trust automated review bot output when reviewing PRs?

Treat bot output only as investigation leads, not conclusions. Distinguish production logic bugs from test fixture drift, generated artifact drift, environment noise, and merge conflicts before reporting any issue.