Get pr comments

Skill giostriquer/agent-workshop/plugins/toolkit/skills/get-pr-comments

Set of plugins of agents and skills for daily ai work

Install

npx -y skills add giostriquer/agent-workshop --skill get-pr-comments

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Fetch and summarize review comments from the active pull request. Use when you need a concise, actionable summary of feedback on the active PR.

SKILL.md

1.6 KB, 321 tokens by cl100k_base, as published. Nobody here has run it

Get PR Comments

Trigger

Use when you need a concise, actionable summary of feedback on the active pull request.

Workflow

Resolve the active PR for the current branch: gh pr view --json number,url,headRefName,state.
Fetch the feedback:
- Conversation comments and review summaries: gh pr view --json comments,reviews.
- Inline review comments on the diff: gh api repos/{owner}/{repo}/pulls/{number}/comments.
Group the feedback by severity (blocking / should-fix / nit) and actionability (a clear change requested vs. an open question).
Return a concise action list ordered by priority, plus the questions that still need a human answer.

Output

Grouped feedback summary (by severity / actionability).
Action list ordered by priority.
Open questions that still need clarification.

Boundaries

Do NOT reply to, resolve, react to, or otherwise respond to any PR comment unless the user explicitly asks you to. This skill reads and summarizes feedback — it never posts a reply, resolves a thread, adds a reaction, or comments on the PR on its own. Posting any response requires an explicit, per-action instruction from the user.
Read-only otherwise: it does not edit code, push, or change PR state. Acting on the feedback is a separate step the user directs.
If there is no active PR for the branch, or gh is unauthenticated, say so plainly rather than guessing.

Gives 0 of the 12 instructions most note taking skills give in 321 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06

include a visual element on every slidein 44 of 686, across 13 files
use wikilinks for internal vault linksin 35 of 686, across 11 files
commit to a single visual motif across every slidein 34 of 686, across 9 files
read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
keep 0.5 inch minimum marginsin 30 of 686, across 7 files
use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
re-verify affected slides after every fixin 27 of 686, across 5 files
run content QA checks before declaring successin 26 of 686, across 3 files
Use Markdown links for external URLs onlyin 26 of 686, across 10 files
pick a bold topic specific color palettein 24 of 686, across 2 files
read editing guide before editing existing presentationsin 23 of 686, across 1 file
use one dominant color across all slidesin 23 of 686, across 1 file

Said here and by no other author read

resolve the active pull request for the current branch
fetch conversation comments and review summaries
fetch inline review comments on the diff
group the feedback by severity and actionability
return a concise action list ordered by priority
return open questions needing a human answer

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.