skills.rest
aizhimou
aizhimouCOMMUNITY
Explore all skills by this author →
Website𝕏@aizhimougGitHub

release-issue-responder

Drafts and posts approved GitHub issue replies based on published release notes.

1.2k|101|Updated Aug 23, 2025
Search Tags:#release management#release notes#issue triage#gh CLI#gitHub#maintainer workflow#issue reply
One-click install
npx skills add https://github.com/aizhimou/pigeon-pod --skill release-issue-responder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-issue-responder
Source: https://github.com/aizhimou/pigeon-pod/tree/main/.agent/skills/release-issue-responder
Command: npx skills add https://github.com/aizhimou/pigeon-pod --skill release-issue-responder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After shipping a release, maintainers must manually find which open GitHub issues are addressed, write replies in each reporter's language, and decide whether to close each issue. This Skill turns that tedious follow-up into a disciplined, approval-gated workflow.

Core Features & Use Cases

  • Release-to-Issue Matching: Reads a release note as the source of truth and matches its shipped changes against open issues fetched with gh issue list.
  • Language-Mirrored Draft Replies: Drafts concise replies in the issue opener's language, connecting release-note items to user-visible outcomes without over-claiming fixes.
  • Approval-Gated Posting and Closing: Presents one draft at a time, posts only after explicit approval via gh issue comment, then recommends closing or keeping open with reasoning.
  • Use Case: After publishing PigeonPod v1.24.0, run this Skill to find all open issues covered by the release note, reply to each reporter in their language, and close the issues that are fully resolved.

Quick Start

Use the release-issue-responder skill to review the v1.24.0 release note, draft replies for matching open GitHub issues, and close the ones I approve.

Frequently Asked Questions about release-issue-responder

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

FAQPage Schema
How do I reply to GitHub issues covered by a new release?▼

Read the release note as the source of truth, list open issues with gh issue list, and match shipped changes to issue reports. Draft one reply at a time, get approval, then post with gh issue comment.

How to close GitHub issues after a release using gh CLI?▼

After posting an approved reply, run gh issue close <number> --repo <owner/repo>. Close only when the release directly satisfies the request; keep issues open when verification or broader root causes remain.

Does the skill reply in the issue author's language?▼

Yes, replies mirror the issue opener's language, preferring it over later commenters' language. A Chinese-language issue gets a Chinese reply, and an English-language issue gets an English reply.

Can the skill post comments without my approval?▼

No, every drafted reply is presented one at a time and posted only after explicit approval of that specific wording. Issue closure also waits for your decision before running gh issue close.

When should an issue stay open after a release reply?▼

Keep an issue open when the fix is related but not exact, multiple root causes exist, third-party compatibility needs confirmation, or the reporter must verify their own setup after upgrading.

Related Skills

Explore More Software Engineering Skills→
masx200masx200
2

github-release

Create GitHub releases from tagged commits using gh CLI.

Community
Advanced
wsmanwsman
18

day-one-patch

Plan post-release patch scope and rollback-safe responses for launch-blocking bugs.

Community
Advanced
Svenja-devSvenja-dev
38

reddit-research

Scan configured subreddits for manufacturing insights and draft replies.

Community
Intermediate
smallnestsmallnest
207

ship-it

Commit changes, create and merge a pull request, and close the linked GitHub issue.

Community
Advanced