Update SYSTEM.md, ADRs, and BACKLOG.md from Git diffs and completed code.
npx skills add https://github.com/peel/fiddle --skill docs-evolve
Please help me install this Agent Skill. Skill: docs-evolve Source: https://github.com/peel/fiddle/tree/main/skills/docs-evolve Command: npx skills add https://github.com/peel/fiddle --skill docs-evolve
This Skill automates the tedious and often neglected task of updating project documentation after code changes, ensuring that documentation remains accurate and reflects the current state of the system.
SYSTEM.md, creates Architecture Decision Records (ADRs), and appends to BACKLOG.md based on completed code.SYSTEM.md with the new component details, create an ADR for the refactoring decision, and log any tech debt found during implementation to the backlog.Run the docs-evolve skill to update documentation for the latest completed epic.
High-intent search queries and answers about installing and using this skill.
To keep documentation in sync with code, you can run this skill to analyze recent Git diffs and completed code artifacts, then automatically update files like SYSTEM.md and append to BACKLOG.md.
You can generate Architecture Decision Records (ADRs) automatically by analyzing completed code units and recent Git diffs to identify significant decisions, then creating ADR files reflecting those architectural choices.
You should update system documentation after completing significant architectural refactoring to ensure files like SYSTEM.md accurately reflect new component details and current system state.
Yes, you can track discovered tech debt by analyzing completed code artifacts and Git diffs for implementation issues, which are then logged as new entries appended to BACKLOG.md.
The best way to maintain technical documentation accuracy is to analyze completed code artifacts and recent Git diffs post-development, proposing and writing targeted changes to documentation files.
Yes, docs-evolve requires context from completed code beans and Git history to accurately analyze architectural changes, significant decisions, and discovered issues for documentation updates.
imMamdouhaboammarAnalyze git history and diffs to extract engineering lessons and design principles.
yknothingAutomate creation and maintenance of technical documentation tied to code changes.
fabiolpgomesGenerate structured user stories from PRDs and manage local git branches.
rcrespodevGenerates Markdown documentation from git diffs with Obsidian-compatible YAML frontmatter.