summarize-issues

Summarizes recurring environment and tooling problems from conversations into a known-issues document.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/SSS08099/mom-system --skill summarize-issues-sss08099
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarize-issues
Source: https://github.com/SSS08099/mom-system/tree/main/.agents/skills/summarize-issues
Command: npx skills add https://github.com/SSS08099/mom-system --skill summarize-issues-sss08099

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After long debugging sessions, recurring environment and tooling problems (encoding errors, path issues, build failures) are easily forgotten, forcing developers to repeat the same trial-and-error. This Skill scans the conversation, identifies recurring infrastructure issues, and records confirmed ones in a persistent known-issues document. ## Core Features & Use Cases - Conversation Scanning: Detects problems that recurred 2+ times or required 3+ attempts, filtering out one-time mistakes and business logic bugs. - Deduplication with Counters: Compares candidates against existing entries in doc/known-issues.md and silently increments the occurrence counter for already-documented issues. - User-Confirmed Documentation: Drafts symptom/root-cause/solution summaries, asks for approval, then appends confirmed issues with an occurrence counter. - Use Case: After a session fighting Windows encoding and JAVA_HOME problems, run the skill to capture proven fixes so future sessions skip the trial-and-error. ## Quick Start Ask the AI to summarize the recurring environment problems from this session and add the confirmed ones to doc/known-issues.md.

Frequently Asked Questions about summarize-issues

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

FAQPage Schema
How do I document recurring environment problems from a debugging session?

Run the summarize-issues skill after your session. It scans the conversation for problems that recurred 2+ times or needed 3+ fix attempts, drafts symptom/root-cause/solution summaries, and writes confirmed entries to doc/known-issues.md.

What kinds of issues does the summarize-issues skill capture?

It captures environment and infrastructure problems such as encoding errors, JAVA_HOME or PATH misconfiguration, cross-platform path handling, Docker lifecycle issues, and database connection failures. It excludes one-time typos and business logic bugs.

Does the skill avoid duplicating already documented issues?

Yes. It reads doc/known-issues.md before writing and compares each candidate against existing entries. Already-documented issues are not shown again; instead their occurrence counter is silently incremented by one.

Can the skill write to the known-issues file without my approval?

No. New issues are always presented to the user for confirmation first. Only after approval are they appended to doc/known-issues.md with an occurrence counter of 1 and a separator.

When should I not use conversation-based issue summarization?

Avoid it for one-off mistakes, normal development iteration, or business logic bugs that were fixed correctly. The skill is designed only for recurring environment and tooling problems with a proven working solution.