Run any Skill in Manus with one click

Get Started

summarize-conversation-thread

Stars1

Forks0

UpdatedMarch 11, 2026 at 20:21

Summarize GitHub issue/PR threads into key decisions, action items, and next steps

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

britt

britt/llpm

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Office Clerks, GeneralOffice and Administrative Support Occupations·SOC 43-9061

SKILL.md

readonly

name	summarize-conversation-thread
description	Summarize GitHub issue/PR threads into key decisions, action items, and next steps
instructions	When summarizing a GitHub issue or PR discussion thread, extracting key decisions, or listing action items from a conversation
tags	["summary","issues","discussion","decisions","action-items"]

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

Output Structure

## 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

## 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.

More from this repository

same repository

architecture-diagramming

britt/llpm

Generate Mermaid architecture diagrams showing system components, layers, and data flows

2026-03-111

at-risk-detection

britt/llpm

Proactively identify at-risk issues and PRs: stale items, blocked work, deadline risks, scope creep, and unassigned high-priority items

2026-03-111

build-faq-from-issues

britt/llpm

Extract common questions from closed GitHub issues and generate an FAQ document with answers

2026-03-111

consolidate-notes-summary

britt/llpm

Search project notes by topic, synthesize findings into a consolidated summary with cross-references

2026-03-111

context-aware-questions

britt/llpm

Proactively identify information gaps in project context and generate actionable questions to surface missing requirements, unclear specifications, or documentation gaps

2026-03-111

dependency-mapping

britt/llpm

Generate Mermaid dependency graphs showing issue relationships, blocking chains, and critical paths

2026-03-111

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

Output Structure

## 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

## 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.