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
Decision gist · record as of 2026-06-03
lwy-knowledge-consolidation saves debugging breakthroughs and config fixes as structured Markdown files stored locally in your project. 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.
Use it when
- lwy-knowledge-consolidation is built for non-trivial problem resolutions, configuration wins, operational procedures, post-mortem lessons.
- lwy-knowledge-consolidation stores your knowledge docs in your project's IDE folder with automated naming and templating.
Verify before relying
Read SKILL.md below before installing (8 files). Open directory: indexed for reading, not audited.
Install
learnwy/skills/lwy-knowledge-consolidation · repository language: TypeScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
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
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Save a debugging breakthrough or config fix as a structured doc in the project”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
lwy-status pulls together progress metrics from every learnwy subsystem—vocabulary mastery, wiki integrity, prompt-optimizer activity, knowledge nudges, and log sizes—into a single consolidated view. Run it on demand or let the weekly SessionStart hook deliver an automated digest at the start of each ISO week.
This skill acts as a prompt coach, evaluating every instruction you send to an AI system across seven key dimensions: clarity, specificity, context, structure, examples, constraints, and completeness. It scores each area, identifies gaps, and delivers a rewritten version designed to produce better results on the first try. Works with any prompt type—code generation, writing, analysis, or creative tasks.
lwy-dispatch coordinates three IDE-hook events (UserPromptSubmit, Stop, SessionStart) shared across learnwy skills, running their scanners in a single process instead of spawning separate Node instances per skill. It aggregates reminders from english-learner, llm-wiki, prompt-optimizer, knowledge-consolidation, and learnwy-status into one combined output per event, cutting per-turn hook latency and reducing system-reminder spam.
lwy-self captures your daily work life—meetings, collaborations, decisions—into a private local diary that grows into a personal knowledge layer. It stores what you did and who you worked with across dated entries, people profiles, and project records, letting your AI assistant know you as a person. Pair it with lwy-llm-wiki to separate personal history from world knowledge.
lwy-project-rules-writer guides you through designing and generating project-specific AI rules that persist across sessions. It analyzes your codebase, confirms the rule design with you, then outputs frontmatter+markdown files to `.agents/rules/` — compatible with Trae, Cursor, Windsurf, and Claude Code. Use it to enforce naming conventions, code style, commit formats, or consistent AI behavior without creating skills or agents.
This skill analyzes your project's tech stack and workflow to recommend the best-matching skills, then installs them to a project-relative path only after you confirm. It detects languages, frameworks, build tools, and testing setups to surface relevant skill options, while delegating skill creation to specialized writers.
More skills lwy-project-agent-writer (MIT) · lwy-project-skill-writer (MIT)