skills.rest
takemi-ohama
takemi-ohamaCOMMUNITY
Explore all skills by this author →
GitHub

review-pr-comments

Classify GitHub PR comments into priority categories and action plans.

Updated Jan 30, 2026
Search Tags:#github#analysis#classification#pr#triage#code-review#read-only
One-click install
npx skills add https://github.com/takemi-ohama/ai-plugins --skill review-pr-comments-takemi-ohama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr-comments
Source: https://github.com/takemi-ohama/ai-plugins/tree/main/plugins/ndf/skills/review-pr-comments
Command: npx skills add https://github.com/takemi-ohama/ai-plugins --skill review-pr-comments-takemi-ohama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams review PR comments without modifying code, enabling fast triage and decision-making.

Core Features & Use Cases

  • Analyze all PR comments on the current branch or a specified PR and categorize them into Major, Improvement recommended, Minor, Reference, or Separate PR tasks.
  • Produce a prioritized action plan for what to fix or address in follow-up PRs, reducing back-and-forth and speeding releases.
  • Use case: a maintainer runs the command to surface actionable items and recommended next steps before making changes.

Quick Start

Run /ndf:review-pr-comments to analyze the PR comments on the current branch, or specify a PR number to target a specific PR and obtain a classification report.

Frequently Asked Questions about review-pr-comments

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

FAQPage Schema
How do I triage GitHub PR comments by priority without modifying code?▼

Triage GitHub PR comments by priority using a read-only analysis tool that classifies feedback into Major, Improvement recommended, Minor, Reference, or Separate PR tasks. It evaluates the current branch or a specified PR to produce a structured action plan without altering code.

What is the best way to categorize code review comments for a follow-up action plan?▼

Categorize code review comments by running a read-only analysis that targets a GitHub PR and sorts feedback into priority levels. This generates a prioritized action plan to address fixes and separate tasks, reducing back-and-forth before releases.

Can I analyze a specific GitHub PR branch instead of the current one?▼

Yes, you can analyze a specific GitHub PR by specifying the PR number. The analysis runs read-only, classifying all comments on that targeted PR to provide a structured triage report for reviewers and developers.

Does the PR comment triage process make any changes to the repository?▼

No, the PR comment triage process is strictly read-only. It uses Bash, Read, Glob, and Grep to evaluate comments deterministically and returns a human-readable classification report without modifying any code or repository state.

How are PR comments classified when preparing for a release?▼

PR comments are classified into five categories: Major, Improvement recommended, Minor, Reference, or Separate PR tasks. This categorization helps maintainers surface actionable items and recommended next steps quickly before merging.

Related Skills

Explore More Software Engineering Skills→
0xdeafcafe0xdeafcafe

review-pr

Audit open GitHub pull requests and return structured read-only reviews.

Community
Advanced
nathanvalenathanvale
2

dx-patterns

Design developer experience patterns for CLIs, toolchains, and documentation.

Community
Intermediate
vecearvecear

quality-gates-enforcer

Enforce coverage, linting, type checking, and security thresholds in CI pipelines.

Community
Advanced
act70255act70255

lint-and-validate

Lint and statically analyze Node.js and Python code with ESLint, Pylint, Ruff, MyPy, and Bandit.

Community
Advanced