update-pr

Fetch GitHub PR comments and render traceability documents as JSON and Markdown.

Updated Apr 19, 2026

Search Tags:#github #traceability #pr-review #renderer #findings #update-pr #draft-replies

Ready to run

npx skills add https://github.com/jewzaam/jewzaam-reviews --skill update-pr-jewzaam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/jewzaam/jewzaam-reviews/tree/main/skills/update-pr
Command: npx skills add https://github.com/jewzaam/jewzaam-reviews --skill update-pr-jewzaam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates incorporating code review feedback from GitHub PRs by collecting comments, mapping them to traceable findings, guiding interactive review decisions, and producing a ready-to-apply set of resolutions and draft replies.

Core Features & Use Cases

Fetch PR comments and supplementary feedback from multiple sources (transcripts, emails, Slack threads) and build a traceability document.
Walk through unresolved comments one-by-one, surfacing contextual before/after when edits are made, and generate a de-risked resolution set.
Emit Finding-level JSON and a rendered Markdown traceability document for review and handoff.

Quick Start

Invoke the update-pr skill on a target PR to begin collecting feedback and generating a traceability document.

Frequently Asked Questions about update-pr

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

FAQPage Schema

How do I map GitHub PR review comments to traceable findings?▼

You can incorporate PR review feedback by fetching inline GitHub comments and supplementary feedback sources like transcripts or chat threads, assigning per-comment traceability, and generating a structured findings document for formal resolution.

Can I use external feedback sources like Slack threads to resolve PR comments before merging?▼

Yes, you can use external feedback sources like Slack threads, transcripts, and emails. The Skill aggregates these supplementary channels alongside GitHub PR comments to build a comprehensive traceability document for formal resolution before merging.

What is the best way to automate generating a traceability document for pull request feedback?▼

Automating PR feedback traceability involves fetching comments, building pre-render JSON, assigning per-comment traceability, and rendering the results into ready-to-review JSON and Markdown documents for handoff.

How do I walk through unresolved PR comments interactively and generate draft replies?▼

To walk through unresolved PR comments interactively, the Skill surfaces contextual before/after edits, guides review decisions, and generates a de-risked resolution set with draft replies.

What file formats are output when rendering PR findings documents?▼

The output file formats are Finding-level JSON and Markdown, specifically generated as Findings-update-pr-<number>.json and Findings-update-pr-<number>.md via the render script.

Does this approach work with GitHub PRs that only have inline comments?▼

Yes, it applies to GitHub PRs with inline comments by fetching the comments, building pre-render JSON, assigning per-comment traceability, and rendering the final findings documents.