Reviews session friction and updates documentation with lessons learned.
npx skills add https://github.com/kma-core/windmill --skill refine-kma-core
Please help me install this Agent Skill. Skill: refine Source: https://github.com/kma-core/windmill/tree/main/.agents/skills/refine Command: npx skills add https://github.com/kma-core/windmill --skill refine-kma-core
git diff main...HEAD --stat and reflection on what was slow, failed, or hard to find. - Targeted Doc Updates: Reads relevant docs (validation.md, enterprise.md, autonomous-mode.md) and proposes minimal, specific edits. - Guardrails: Only adds session-confirmed knowledge, keeps additions concise, and avoids speculative or generic content. - Use Case: After a long debugging session where a validation rule was missing, run this Skill to add that rule to the validation matrix so the next session catches it immediately. ## Quick Start Ask the assistant to run the refine skill to review this session and update the docs with lessons learned.High-intent search queries and answers about installing and using this skill.
Run the refine skill at the end of a session. It inspects what files changed with git diff, reflects on friction points like failures or missing information, and edits the relevant docs files with concise, confirmed updates.
Use an end-of-session reflection workflow that reviews what went wrong during work and updates docs accordingly. The refine skill reads existing docs, identifies missing knowledge or wrong guidance, and applies minimal targeted edits.
It adds missing knowledge discovered during the session, corrects wrong guidance, adds missing validation rules, and captures new codebase patterns. It only adds knowledge confirmed by the session and keeps changes to a line or two.
Avoid it when the session produced no confirmed new knowledge, since the skill explicitly rejects speculative additions. It is also not suited for large documentation rewrites, as it is designed for minimal, incremental updates.
It avoids updating skills unless a coding pattern was genuinely wrong. If a whole new document is warranted, it creates it in the docs directory and adds a pointer in CLAUDE.md.
berserkdisruptorsReconstruct development context from git commit history into structured intent and decision lines.
az0512124155azz-sysUpdates an existing pull request with new commits and refreshed metadata.
douglanceWrite and verify README, API, and ADR documentation against shipped code behavior.
mpauloskyRecord only confirmed final outcomes in history.md and decision logs.