respond

Draft tone-matched maintainer responses for open GitHub issues and pull requests.

3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Abhilash-003/mstack --skill respond-abhilash-003
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: respond
Source: https://github.com/Abhilash-003/mstack/tree/main/respond
Command: npx skills add https://github.com/Abhilash-003/mstack --skill respond-abhilash-003

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MStack helps maintainers respond faster to GitHub issues and PRs by drafting tone-matched replies from templates and recent maintainer comments, while requiring explicit human approval before anything is posted.

Core Features & Use Cases

  • Finds items needing responses: drafts for open issues with no maintainer comments and open non-draft PRs without a review decision.
  • Learns the repo’s voice: reads recent human issue comments to mirror formality, emoji usage, length, greeting style, punctuation habits, and technical formatting.
  • Scenario-based drafting with templates: selects a scenario (needs-info, duplicate, welcome, bug-confirmed, wont-fix, stale-close, pr-feedback, general-thanks) and fills the appropriate response template when applicable.
  • Human approval required: presents each draft item-by-item for posting, editing, or skipping, then posts via the GitHub CLI only after confirmation.

Quick Start

Use respond to draft replies for open issues and PRs in the configured repo, by asking Claude to run: run mstack respond

Frequently Asked Questions about respond

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

FAQPage Schema
How do I automate maintainer replies for GitHub issues and pull requests?

You can automate maintainer replies by drafting tone-matched responses for open GitHub issues and PRs that lack a maintainer comment or review decision, requiring explicit human approval before posting via the GitHub CLI.

How does tone matching work when drafting GitHub issue responses?

Tone matching works by reading recent human issue comments to mirror the repo's formality, emoji usage, length, greeting style, punctuation habits, and technical formatting in the drafted responses.

What scenarios can automated response drafting handle for GitHub issue triage?

Automated response drafting handles issue triage scenarios including needs-info, duplicates, welcomes, bug confirmations, wont-fix, stale closings, PR feedback, and general thanks by filling the appropriate response template.

Do I need the GitHub CLI to draft and post maintainer responses?

Yes, the GitHub CLI must be available and authenticated to draft and post maintainer responses, as the skill posts approved replies through the GitHub CLI after explicit human confirmation.

Can I review and edit drafted GitHub replies before they are posted?

Yes, you can review, edit, or skip drafted GitHub replies item-by-item before posting, as the skill presents each draft for explicit human approval and only posts after confirmation.

What is the best way to handle stale GitHub issues that need closing?

The best way to handle stale GitHub issues is using scenario-based drafting to generate stale-close responses from templates, matching the repo's tone, and posting them after explicit human approval.