summarize-conversation-thread
/summarize-conversation-thread
Use when catching up on a long GitHub issue or PR discussion thread, or asked to summarize a thread, extract key decisions, or list action items - produces a structured summary with TL;DR, decisions, action items, open questions, and next steps
- Author
- britt ↗
- Repository
- claude-code-skills ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when catching up on a long GitHub issue or PR discussion thread, or asked to summarize a thread, extract key decisions, or list action items - produces a structured summary with TL;DR, decisions, action items, open questions, and next steps
Original author description
Use when catching up on a long GitHub issue or PR discussion thread, or asked to summarize a thread, extract key decisions, or list action items - produces a structured summary with TL;DR, decisions, action items, open questions, and next steps
How it works
- When to Use
- Getting the Thread
- Output Structure
- Guidelines
- Example
SKILL.md preview
--- name: summarize-conversation-thread description: "Use when catching up on a long GitHub issue or PR discussion thread, or asked to summarize a thread, extract key decisions, or list action items - produces a structured summary with TL;DR, decisions, action items, open questions, and next steps" --- # Summarize Conversation Thread Skill Read long GitHub issue or PR threads and produce concise summaries highlighting what matters. ## When to Use Activate when: - Catching up on a lengthy discussion - Preparing to contribute to an existing thread - Extracting decisions from a closed issue - Identifying action items from a discussion **When NOT to use:** Skip for short threads (fewer than ~5 comments) — just read them directly. ## Getting the Thread First, obtain the full thread content: - **Issues**: `gh issue view <number> --comments` (requires the `gh` CLI, authenticated) - **PRs**: `gh pr view <number> --comments` - **No gh CLI or no repo access**: Ask the user to paste the thread content ## Output Structure ```markdown ## Summary: [Issue/PR Title] **Status**: [Open/Closed] | **Comments**: [X] | **Last Activity**: [date] ### TL;DR [2-3 sentence summary of the core discussion] ### Key Decisions - **[Decision]**: [context and who decided] ### Action Items - [ ] [Action] — @[owner] ### Open Questions - [Unresolved question needing input] ### Next Steps [What should happen next] ``` ## Guidelines ### What to Include - Decisions made and who made them - Action items with clear owners - Unresolved questions or blockers - Changes in direction or scope - Links to key comments ### What to Skip - Redundant "+1" or "me too" comments - Off-topic tangents - Superseded proposals - Resolved sub-discussions ### Handling Edge Cases - **Stale threads** (>30 days inactive): Note this and flag if decisions may be outdated - **Heated discussions**: Present all perspectives neutrally - **No resolution**: Clearly state "No decision reached" and summarize options discussed - **Long threads** (50+ comments): Break into phases if discussion evolved significantly ## Example ```markdown ## Summary: Add dark mode support (#142) **Status**: Open | **Comments**: 23 | **Last Activity**: 2 days ago ### TL;DR Team agreed to implement dark mode using CSS variables. Debate on whether to auto-detect system preference or default to light mode resolved in favor of auto-detect. ### Key Decisions - **Use CSS variables**: Easier to maintain than separate stylesheets — @sarah - **Auto-detect system preference**: Better UX, users can override — @mike ### Action Items - [ ] Create color token system — @sarah - [ ] Add toggle to settings page — @alex ### Next Steps Sarah to submit initial PR with color variables by Friday. ```
Versions
The database has no other skills named summarize-conversation-thread.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 1127f87fb4fa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90email-thread-summarizer
Summarize a long email thread into its current state, the decisions and key points, and the open questions. Finds the thread with browse_engagements (emails), then uses conversation_intelligence with includeContent to read the actual thread body. Name the account, contact, or… - 100review-github-pr
Review a GitHub pull request by summarizing its diff and key design decisions. Use when the user wants to review a PR, understand changes in a branch, or get a code review summary. Trigger keywords - review PR, review pull request, summarize PR, summarize diff, code review,… - 96thread
Use only when the owner asks for a thread. Opens a branch. - 100summarize
Use when the user wants to summarize, condense, digest, or extract the key points / TL;DR / executive summary / action items / minutes from any source — pasted text, a file, an email or email thread (Outlook), a Confluence page (optionally with all its subpages), a wiki page, or… - 100thread-to-action
Parses a pasted thread (Slack, email, GitHub, Teams), analyzes it against current git, Linear, and session context, and suggests actionable next steps — then executes them with confirmation. Use when pasting a conversation that implies developer actions. - 100meeting-notes-to-actions
Transforms meeting transcripts, raw notes, or audio transcriptions into structured outputs: key decisions made, owned action items with deadlines, open questions, and a concise executive recap. Supports multiple output formats. Use when asked to 'summarize this meeting',…