skills.rest
lexmount
lexmountOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-review-checklist

Generate Markdown PR review checklists from GitHub review threads and code context.

19|5|Updated May 9, 2026
Search Tags:#automation#developer tools#code review#checklist#pull request#github
One-click install
npx skills add https://github.com/lexmount/browseruse-agent-bench --skill pr-review-checklist-lexmount
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-checklist
Source: https://github.com/lexmount/browseruse-agent-bench/tree/main/browseruse_bench/skills/pr-review-checklist
Command: npx skills add https://github.com/lexmount/browseruse-agent-bench --skill pr-review-checklist-lexmount

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the challenge of managing fragmented feedback across GitHub pull request threads by centralizing comments, code context, and resolution status into organized, actionable Markdown checklists.

Core Features & Use Cases

  • Automated Tracking: Automatically pulls review threads and comments from GitHub to generate persistent checklists.
  • Contextual Awareness: Maps review comments to specific code locations, providing diff hunks and local file context for easier debugging.
  • Use Case: Use this to maintain a clear, up-to-date list of unresolved review items during a complex code review process, ensuring no feedback is missed before merging.

Quick Start

Run the pr-review-checklist script to generate a review checklist for the current branch pull request.

Frequently Asked Questions about pr-review-checklist

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

FAQPage Schema
How do I track unresolved GitHub pull request comments in a checklist?▼

You can track unresolved GitHub pull request comments by aggregating review threads into a persistent Markdown checklist. This automatically maps feedback to code locations and maintains resolution status across iterations.

How do I generate a code review checklist from GitHub review threads?▼

Generate a code review checklist by pulling GitHub review threads and mapping them to current file contents. This creates an actionable list with diff hunks and local file context for easier debugging.

Do I need the GitHub CLI to automate pull request review tracking?▼

Yes, you need the GitHub CLI to fetch pull request thread data. The tool requires local repository access and the CLI to aggregate comments and map them to current file contents.

Can I maintain unresolved code review items across multiple pull request iterations?▼

Yes, you can maintain unresolved code review items across multiple iterations. The checklist tracks resolution status by continuously aggregating GitHub review threads and updating the code context.

What is the best way to organize fragmented GitHub PR review feedback?▼

Organize fragmented GitHub PR review feedback by centralizing comments and code context into structured Markdown checklists. This maps review comments to specific code locations for actionable tracking.

Why does my code review checklist not showing local file context for GitHub comments?▼

The checklist requires local repository access to map GitHub comments to specific code locations. Without local file access, it cannot fetch thread data or provide diff hunks for debugging.

Related Skills

Explore More Software Engineering Skills→
photon-grovephoton-grove
1

status

Summarize open pull requests, issues, and stuck items in a GitHub repository.

Official
Intermediate
dobrinz123dobrinz123

gsd-ship

Push branches, create pull requests, and monitor merge status.

Community
Intermediate
dceoydceoy
2

local-qa

Runs formatting, linting, and testing scripts on a code repository.

Community
Intermediate
shogoggshogogg
4

fetch-pr-review-comments

Fetch unresolved review comments from the current branch's GitHub pull request.

Community
Advanced