issue-resolve

Locate resolution files in change-summary matching the latest issue-summary record.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When issues and their fixes are documented in separate markdown folders, finding the resolution for a previously recorded problem requires manual searching. This Skill automates the lookup by pairing issue-summary records with their corresponding change-summary resolution files. ## Core Features & Use Cases - Latest Issue Detection: Lists markdown files in issue-summary/ and picks the most recent by timestamp or modification time. - User Confirmation Loop: Presents the candidate issue and iterates through older records until the user confirms the right one. - Naming-Convention Resolution Lookup: Derives the resolution filename by appending "-resolution" to the issue file's base name and reads it from change-summary/. - Use Case: After documenting a bug with issue-summarize, you later ask "看看之前那个问题怎么解决的" and the Skill retrieves the matching fix record instantly. ## Quick Start Ask the assistant to find how the previously recorded issue was resolved and show the fix from the change-summary folder.

Frequently Asked Questions about issue-resolve

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

FAQPage Schema
How do I find the resolution for a previously documented issue?

The Skill lists markdown files in issue-summary/, picks the most recent one, confirms it with you, then looks for a file with the same base name plus a -resolution suffix in change-summary/ and presents its contents.

What naming convention links issue records to resolution files?

An issue file named issue-summary/{slug}-{timestamp}.md maps to change-summary/{slug}-{timestamp}-resolution.md. The Skill extracts the base name from the issue file and appends -resolution to locate the fix record.

What happens if no resolution file exists for an issue?

The Skill reports that no corresponding resolution file was found in change-summary/ and suggests the issue may not be fixed yet or the fix was never documented. It does not fail or guess at other files.

Can I look up an older issue instead of the most recent one?

Yes. When the Skill presents the latest issue record, you can say it is not the right one, and it will show the next most recent file, repeating until you confirm the correct issue or abort the search.

What are the limitations of filename-based resolution lookup?

The lookup depends entirely on the strict naming convention of matching base names plus the -resolution suffix. Files renamed manually or stored outside issue-summary/ and change-summary/ will not be matched.