skills.rest
SSS08099
SSS08099COMMUNITY
Explore all skills by this author →
GitHub

issue-summarize

Writes a structured markdown problem summary file documenting failed bug fix attempts.

Updated Jun 16, 2026
Search Tags:#debugging#documentation#markdown#bug tracking#issue summary#problem recording#fix attempts
One-click install
npx skills add https://github.com/SSS08099/mom-system --skill issue-summarize-sss08099
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-summarize
Source: https://github.com/SSS08099/mom-system/tree/main/.agents/skills/issue-summarize
Command: npx skills add https://github.com/SSS08099/mom-system --skill issue-summarize-sss08099

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a bug resists one or two fix attempts, continuing to guess wastes effort and loses context. This Skill forces a pause by capturing the problem, related code, and failed attempts into a persistent markdown file for later analysis. ## Core Features & Use Cases - Structured Issue Documentation: Generates a timestamped markdown file in issue-summary/ with problem description, related code references with line numbers, and a log of attempted fixes. - Proactive Triggering: Activates automatically after two failed fix attempts on the same issue, or when the user asks to record or summarize a bug. - Read-Only Discipline: Strictly produces only the summary file without modifying any code, ensuring the pause is respected. - Use Case: After two unsuccessful attempts to fix a form refresh bug in a Vue project, ask the assistant to record the issue; it writes issue-summary/tab-refresh-redirect-20260620-1430.md documenting symptoms, code locations, and why each fix failed. ## Quick Start Ask the assistant to summarize this bug and record it as an issue after your fix attempts have failed.

Frequently Asked Questions about issue-summarize

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

FAQPage Schema
How do I document a bug that keeps failing to get fixed?▼

Ask the assistant to summarize the problem or record the issue. It writes a markdown file to the issue-summary directory containing the problem description, related code with line numbers, and each attempted fix with why it failed.

When should I write an issue summary instead of trying another fix?▼

Write a summary after two failed attempts to fix the same bug when the symptom persists. The summary forces a pause, captures context, and prevents wasted effort on repeated wrong approaches before trying a new angle.

What information goes into a bug summary document?▼

A bug summary includes the problem description in the reporter's words, a table of related files with line numbers and key code snippets, each attempted fix with its result, and a disclaimer noting the documented approaches were dead ends.

Does writing an issue summary modify my source code?▼

No. The skill has a hard constraint to only create one markdown file in the issue-summary directory and never modifies any code. Requests to check for other problems are answered within the summary, not through code changes.

Why create a new summary file instead of updating an old one?▼

Each summary gets a fresh timestamped filename so old files are never overwritten. Keeping historical summaries preserves the evolution of understanding about a problem, which is valuable when revisiting recurring issues.

Related Skills

Explore More Software Engineering Skills→
jonkikyjonkiky

investigate

Trace reported issue symptoms to code paths and verify root cause hypotheses.

Community
Advanced
0xHarbs0xHarbs
1

debug

Diagnose failures by applying hypothesis-driven root-cause analysis to test outputs, stack traces, and CI logs.

Community
Advanced
Mte90Mte90
51

Jira Integration

Retrieve Jira issue details and link Zephyr test cases.

Community
Intermediate
SuperClaude-OrgSuperClaude-Org
23.9k

troubleshoot

Diagnose errors and bugs through systematic root cause analysis.

Official
Basic