forge-respond

Triages unresolved GitHub PR review threads and executes approved fixes, deferrals, and replies.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill forge-respond-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-respond
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/forge-respond
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill forge-respond-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Responding to a pile of PR review comments is error-prone: threads get missed, fixes ship without replies, and follow-up work is never tracked. This Skill structures the entire review-response cycle with a human approval gate so nothing is acted on without sign-off. ## Core Features & Use Cases - Automated triage: Fetches unresolved review threads, formal review submissions, and PR-level comments via the GitHub CLI and GraphQL API, then categorizes each item as Fix Now, Defer, or Ignore. - Human approval gate: Presents a triage table and blocks all execution until the user approves or overrides individual items with commands like "1 defer" or "3 fix now". - Execution and tracking: Implements approved code fixes in a single commit, creates follow-up GitHub issues for deferred items, posts thread replies, resolves threads, and publishes a summary comment on the PR. - Use Case: After a reviewer leaves twelve comments on your pull request, run the skill to get a triaged action plan, approve it, and have fixes committed, issues created, and threads resolved automatically. ## Quick Start Ask the assistant to respond to all review comments on pull request 42 using the forge-respond workflow.

Frequently Asked Questions about forge-respond

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

FAQPage Schema
How do I respond to all PR review comments at once on GitHub?

Invoke the skill with the PR number and it fetches all unresolved review threads, formal reviews, and PR-level comments via the GitHub CLI. Each item is triaged into Fix Now, Defer, or Ignore, then executed only after you approve the triage table.

How to triage code review feedback into fixes and follow-up issues?

The skill applies heuristics to each comment: blocking language and bug reports become Fix Now, out-of-scope suggestions become Defer, and nits become Ignore. Deferred items automatically get GitHub issues created with links back to the original comment.

Can I override the automated triage decisions before changes are made?

Yes, a hard approval gate blocks all execution until you respond. You can approve as-is or override items with commands like "1 defer", "3 fix now", or attach notes such as "2 note: track as bug" before anything is committed or posted.

Does this work with review comments that have no inline thread?

Yes, PR-level comments without a thread_id are handled separately. Fixes are delivered via the commit itself, deferrals create issues plus a new PR comment, and declines are explained through a new PR comment since no inline reply is possible.

What happens if replying to a review thread or resolving it fails?

Failures are logged with the item id, action, and error message, and processing continues with remaining items. All errors are reported in the final summary posted as a PR comment.