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
Manage a personal knowledge base by adding, searching, organizing, and reviewing articles, links, and notes with tags and natural language queries.
Generate a daily work report by automatically discovering all git repositories the user worked on, collecting commit logs across all branches, and summarizin...
日记引导助手。每日写作引导、感恩日记、反思日记、晨间日记、晚间总结、周总结模板。Journal prompts for daily writing, gratitude, reflection, morning pages, evening review, weekly summary. 日记、写作、反思、感恩。
Use when maintaining RDR2 (Red Dead Redemption 2) playthrough notes — logging an acquisition ("acquired X", "got N gold bars", "finished X"), answering in-game location/crafting questions, or reviewing the notes for duplicate or stale info. Triggers on RDR2, Red Dead Redemption, playthrough, legendary animal, talisman, trinket, valerian root, gold bar, horse, weapon, berry.
Microsoft OneNote integration. Manage Notebooks. Use when the user wants to interact with Microsoft OneNote data.
Use when a sales rep already has a customer who has expressed some need (from outreach follow-up, account-landing research, customer-initiated contact, or meeting notes) and needs to structurally validate whether that need is real, urgent, whose pain it actually is, and whether it matches the team's capability — before pushing to ROI proofing or buying-intent assessment. Triggers: '验证一下这个需求是不是真的', '需求真不真', '客户说痛但我不确定', '这个客户值不值得跟', '客户说会考虑但是真的吗', '谁拍板', '现有方案是什么', '切换成本', 'need validation', 'pain point validation', 'is this a real need', 'verify customer need'. Do NOT use for: scoring leads at line-item level, building target-customer profiles, calculating ROI, overall buying-intent scoring, opportunity-stage assessment, or writing outreach/cold messages.