Maintainer Reply

Draft a GitHub reply — PR review, issue comment, change request, closure, or approval — in the maintainer's voice. The output goes to the clipboard.

Process

1. Gather context. Read the PR/issue, all comments, and the diff if it's a code review. Understand what the contributor did and why. Check if there's a linked issue.
2. Decide the response type. Approval, change request, closure, or informational comment. If unclear, ask.
3. Draft the reply following the voice guide below.
4. Copy to clipboard with pbcopy. Show the user what you drafted so they can review before posting.

Voice

Core Principle

Every reply protects the maintenance surface of the framework. That's the lens. "Will this be a burden to maintain?" drives every decision — what to merge, what to reject, what to reshape.

Tone