resolve-discussion

Summarize GitHub discussion issues, propose options, and post decision comments.

9|2|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/typemd/typemd --skill resolve-discussion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-discussion
Source: https://github.com/typemd/typemd/tree/main/.claude/skills/resolve-discussion
Command: npx skills add https://github.com/typemd/typemd --skill resolve-discussion

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Open GitHub discussion issues often leave decisions undocumented and action items unclear; this Skill helps maintainers drive those conversations to a concrete outcome, document the conclusions in the issue, and mark the discussion as resolved without closing the implementation issue.

## Core Features & Use Cases

  • Select and validate a discussion issue by number, by release-scoped sub-issues, or from all open discussion-labeled issues and confirm with the user before proceeding.
  • Research and summarize relevant context from the repository and sub-issues, surface open questions, and propose 2–3 approaches with trade-offs.
  • Facilitate decisions and document outcomes by capturing user choices, posting a summary comment, creating follow-up issues for actionable work, and removing the discussion label.
  • Use Cases: wrapping up design debates before development, finalizing scope decisions for a release, and turning community debates into tracked follow-ups.

Quick Start

Ask the assistant to resolve discussion #42 by researching the issue, proposing options, recording each decision in a summary comment, creating follow-ups if needed, and removing the discussion label.

Frequently Asked Questions about resolve-discussion

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

FAQPage Schema
How do I resolve GitHub discussion issues and document the final decision?

To resolve GitHub discussion issues, the Skill researches the issue context, proposes 2–3 approaches with trade-offs, captures user choices, and documents decisions as a summary comment before removing the discussion label.

Can I create follow-up issues from a GitHub discussion without closing the original issue?

Yes, this Skill creates follow-up issues for actionable work via scripts and removes the discussion label, leaving the original implementation issue open for development instead of closing it.

What is the best way to triage open discussion-labeled issues across a repository?

Triage open discussion-labeled issues by selecting them individually by number, through release-scoped sub-issues, or from all open issues, then summarize findings and ask clarifying questions to drive conversations to concrete outcomes.

Do I need GitHub CLI access to turn discussion issues into clear decisions?

Yes, GitHub CLI access and issue context are required to fetch issue details and labels, post comments, create follow-up issues, and remove the discussion label during the triage process.

How does this approach handle wrapping up design debates before development starts?

It facilitates decisions by surfacing open questions from repository context and sub-issues, proposing options, recording each decision in a summary comment, and creating tracked follow-ups to finalize scope before implementation.