docs-change-recordsDocumentation engineer skill for module docs, README updates, architecture notes, API change records, and repository-safe documentation placement.
Install via ClawdBot CLI:
clawdbot install aiweline/docs-change-recordsGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 23, 2026
When a code change alters module behavior, usage, or configuration, the skill updates the module's README to reflect the new interface, parameters, or dependencies. This ensures developers using the module have accurate, up-to-date documentation without sifting through code diffs.
Following a system architecture change, such as introducing a new microservice or refactoring a component, the skill updates architecture notes to describe the new design, data flow, and interactions. This maintains a reliable high-level reference for the engineering team.
When an API endpoint or method signature changes, the skill updates API documentation to match the new interface, including parameters, return types, and error codes. This prevents integration failures for dependent services and developers.
After a bug fix that affects user-visible behavior, the skill adds a fix note inside the module's doc directory (not repository root) and updates the module README with a brief change record. This keeps documentation accurate without cluttering root-level files.
The skill enforces the rule that detailed fix reports and troubleshooting logs must be stored in module-local doc directories, not the repository root. This maintains repository cleanliness and avoids confusion for new contributors.
Offer automated documentation updates as part of a DevOps platform, where the skill integrates with CI/CD pipelines to keep project documentation current with code changes. Revenue comes from subscription fees based on repository count or team size.
Provide specialized documentation engineering services to open source projects, ensuring that READMEs, architecture docs, and API docs remain accurate after each release. Revenue is generated through project sponsorships or paid support contracts.
License the skill to enterprises that require auditable documentation changes for regulatory compliance. The skill automates the generation of change records and location-appropriate documentation updates, reducing manual effort and audit risks.
💬 Integration Tip
Integrate the skill as a post-commit hook or CI step to automatically trigger documentation updates when code changes are detected. Pair it with a code review tool to ensure documentation changes are reviewed alongside code changes.
Scored May 23, 2026
Work with Obsidian vaults (plain Markdown notes) and automate via notesmd-cli.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Obsidian笔记库按KG笔记法整理——四种笔记类型、链接权限、关系中转、命名规范、新旧分离。自动纠错+建关系+去重+补缺+无关内容分离+分层加载
Manage a personal knowledge base by adding, searching, organizing, and reviewing articles, links, and notes with tags and natural language queries.
Automatically extract key points from long texts in Chinese or English using keywords or length triggers, outputting clear, concise bullet-point summaries.
Generate a daily work report by automatically discovering all git repositories the user worked on, collecting commit logs across all branches, and summarizin...