pr-comments

Featured

Use when the user asks to review pull request comments, or when the /pr_comments command runs — fetch and analyze PR review comments on the current branch and summarize actionable items.

Code & Development 2,222 stars 97 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
42
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Pull Request Comments Review Review the pull request comments associated with the current branch and turn them into an actionable summary. ## Procedure 1. Identify the PR for the current branch (git remote, branch name → PR). If no PR is found or git hosting tools are unavailable, say so and fall back to reviewing local uncommitted changes. 2. Gather review comments (inline + general) and group them by theme: blocking changes, open questions, nits. 3. For each actionable comment: restate the concern in your own words, locate the affected code, and propose a concrete change. 4. Produce a summary: what the reviewers want changed, what's already addressed, and a suggested order of work. ## Constraints - Never invent comments — summarize only what is actually there. - Mark unresolved vs resolved comments explicitly.

Details

Author
ccch1mneyyy
Repository
ccch1mneyyy/dsh-TUI
Created
1 weeks ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category