Convert debugging outcomes and technical decisions into evidence-backed Case, Decision, and Pattern records.
npx skills add https://github.com/mykcs/myk-skills --skill record-case
Please help me install this Agent Skill. Skill: record-case Source: https://github.com/mykcs/myk-skills/tree/main/record-case Command: npx skills add https://github.com/mykcs/myk-skills --skill record-case
This Skill helps you systematically archive what you learned from debugging, repeated workflow mistakes, and technical decisions so it becomes searchable, reusable knowledge instead of staying trapped in chat logs.
Record a bug fix or a workflow lesson by telling the AI to “record this /归档/留档/case 一下/学到了,” and include the key symptoms, what you tried, and how you verified the final outcome.
High-intent search queries and answers about installing and using this skill.
To archive debugging outcomes into reusable knowledge, you provide the symptoms, attempts, and verified results, and the system extracts facts to generate evidence-backed Case, Decision, or Pattern records. It routes content by priority and enforces structured failure-path reconstruction.
Maintaining a technical decision log for postmortems requires evidence-based documentation that captures non-trivial decision rationale and trigger-style lessons. The system classifies entries into Decision templates and appends them to a memory index with duplication prevention.
Recording workflow mistakes into searchable memory involves stepwise extraction of facts from the event to create lightweight Pattern records. These records append directly to your memory index under dedicated sections, preventing future repeated errors.
Yes, the knowledge management system checks for duplicate case archives by performing a keyword grep before committing. It ensures new evidence-backed records are appended correctly without redundant entries in your stored memory index.
If you provide insufficient details for a postmortem record, the system asks targeted follow-up questions instead of guessing. It requires observable symptoms, commands, and environment or version information to enforce deep Case quality guardrails.
Routing a debugging lesson to a Case versus a Pattern template depends on depth: Cases require deep evidence-backed failure-path reconstruction, while Patterns are lightweight workflow preferences. The system automatically prioritizes Case > Decision > Pattern.
ambient-codeReproduce reported bugs and document observable behavior with minimal test cases.
GoldziherAccess Architecture Decision Records and design rationales for the Spikard project.
kid0317Store fragmented work reflections as searchable, categorized notes in memory archives.
Pear-CommerceAppend timestamped notes and promote them to todos in GSD workflows.
