pr-comment-drafting

Draft concise developer-voice replies to GitHub pull request review threads.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zcawood-mie/agentz --skill pr-comment-drafting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-comment-drafting
Source: https://github.com/zcawood-mie/agentz/tree/main/skills/pr-comment-drafting
Command: npx skills add https://github.com/zcawood-mie/agentz --skill pr-comment-drafting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, concise, and human-sounding replies to pull request review comments can be time consuming and easy to over-explain; this Skill reduces the friction of composing developer-voice responses that address reviewer concerns without unnecessary filler.

Core Features & Use Cases

  • Context-aware drafting: Emphasizes researching the actual code before composing a reply so responses are accurate and justified.
  • Developer voice: Produces short, informal replies that read like a normal developer instead of a formal or corporate statement.
  • Review workflow integration: Drafts replies for PR threads, reviewer questions, and code review comments while enforcing a draft-first, user-approval-before-posting policy.
  • Use case: Respond quickly to a reviewer asking why a function was implemented a certain way by explaining the reason succinctly and proposing an action or clarification.

Quick Start

Draft a concise, developer-voice reply to the latest PR review comment that explains why the code is implemented that way and proposes a next step, then await my approval before posting.

Frequently Asked Questions about pr-comment-drafting

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

FAQPage Schema
How do I draft replies to GitHub pull request review comments?

Drafting PR comment replies requires researching the actual code context first to ensure accuracy, then composing a concise, developer-voice response that addresses the reviewer's concern without unnecessary filler.

What is the best way to write natural code review replies without sounding formal?

Natural code review replies are produced by researching the code context, drafting short and informal responses that read like a normal developer, and applying minimal inline formatting to keep the communication straightforward.

Can I automatically post PR comment drafts directly to GitHub review threads?

No, PR comment drafts are not posted automatically; the workflow enforces a draft-first policy that waits for explicit user approval before posting any reply to a pull request review thread.

Does PR comment drafting work for answering reviewer questions about code implementation?

Yes, PR comment drafting works for reviewer questions by researching the code context to explain why a function was implemented a certain way, proposing a next step, and maintaining a concise developer voice.

What are the limitations of using automated draft replies for code review threads?

Automated draft replies are limited by their dependency on researching code context for accuracy, and they require user approval before posting, meaning they cannot autonomously handle continuous or real-time review thread interactions.

How do I ensure my pull request comment replies are concise and accurate?

Concise and accurate PR comment replies are ensured by a drafting process that prioritizes researching the actual code before composing, producing minimal inline formatting, and enforcing user approval prior to posting.