lwy-knowledge-consolidation
Capture debugging breakthroughs, configuration wins, and operational lessons as structured Markdown files anchored to your project's IDE folder. Each insight becomes a dated, searchable doc that travels with your codebase and surfaces in future sessions on the same project. When a doc proves reusable across projects, promote it into the global knowledge wiki.
lwy-knowledge-consolidation saves debugging breakthroughs and config fixes as structured Markdown files stored locally in your project.
AI-generated summary based on this skill's SKILL.md
Install
learnwy/skills/lwy-knowledge-consolidation · repository language: TypeScript
git clone https://github.com/learnwy/skills
cp -r skills/skills/lwy-knowledge-consolidation ~/.claude/skills/lwy-knowledge-consolidationFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I save this debugging fix to the project?
lwy-knowledge-consolidation lets you capture debugging breakthroughs as structured Markdown files stored in your project's IDE folder. When you document a fix, it becomes a dated, searchable record that travels with your codebase and surfaces automatically in future sessions on the same project, so you never lose the context of how you solved it.
What should I document with lwy-knowledge-consolidation?
lwy-knowledge-consolidation is built for non-trivial problem resolutions, configuration wins, operational procedures, post-mortem lessons, and workflow steps. Save debugging breakthroughs, race condition fixes, deployment rollback procedures, and any insight that took effort to discover—anything you'd want to remember or share with teammates working on this codebase later.
How do I keep debugging notes with my code?
lwy-knowledge-consolidation stores your knowledge docs in your project's IDE folder with automated naming and templating, so they stay anchored to the codebase itself. Each doc is dated and searchable, making it easy to find past solutions when you hit similar problems in future sessions on the same project.
Can lwy-knowledge-consolidation promote docs to a global wiki?
Yes. lwy-knowledge-consolidation lets you promote project-local knowledge to a global wiki when it becomes reusable across multiple projects. Start by capturing insights locally with your codebase, then graduate them to shared knowledge when they prove valuable beyond a single project.
What format does lwy-knowledge-consolidation use for docs?
lwy-knowledge-consolidation creates structured Markdown files with automated naming and templating, making docs consistent and easy to organize. Each file is dated and searchable, so you can quickly surface past fixes and lessons learned whenever you need them during development sessions.
SKILL.md
rendered from the published skill — quoted content, verbatim
Knowledge Consolidation
Project-local fix journal. One conversation → one structured Markdown file in this repo's IDE folder. Stays with the codebase; ships in the repo; future sessions on this project can find it.
> Boundary: project-local debugging/config/workflow/lesson notes belong here.
> Global, reusable knowledge (architectures, design patterns, API integrations, references) belongs in llm-wiki. KC's promote command moves a doc across the seam when it earns its way into the wiki.
When to use
| Trigger | Action |
|---|---|
| User says "save this", "记录下来", "we solved it" | Run cli.cjs save … |
| Stop nudge fired ("looks |
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 8 files
skills/lwy-knowledge-consolidation/SKILL.md
skills/lwy-knowledge-consolidation/assets/knowledge.md.template
skills/lwy-knowledge-consolidation/examples/debug-session.md
skills/lwy-knowledge-consolidation/hooks.json
skills/lwy-knowledge-consolidation/references/conditional-reflection.md
skills/lwy-knowledge-consolidation/references/knowledge-types.md
skills/lwy-knowledge-consolidation/scripts/cli.cjs
skills/lwy-knowledge-consolidation/scripts/hooks/post-resolution-nudge.cjs