skill-improver

To improve documentation based on usage notes, you can analyze a SKILL.md file alongside its SKILL_NOTES.md to identify actionable patterns and generate a minimal, reviewer-approved diff for safe updates.

The best way to generate a diff from workflow observations is to identify actionable patterns in the notes and propose precise, minimal changes that respect structural invariants and require human approval before application.

No, you cannot automate skill-improvement changes without human review. The workflow requires explicit human confirmation before applying any generated diffs to ensure safety and validate structural guardrails.

You validate frontmatter and section order by enforcing structural invariants and safety checks before applying changes, ensuring the documentation respects size constraints and maintains its required section sequence.

To run a skill review workflow, you need the target skill's SKILL.md and SKILL_NOTES.md files, which provide the base documentation and the usage observations required to propose improvements.