sdd-docs

Update CHANGELOG, README, and ADRs after approved code reviews.

1|Updated Apr 25, 2026

Search Tags:#code review #documentation #version control #sdd #change tracking

Ready to run

npx skills add https://github.com/dariomazzitellireplik-coder/sdd-skills --skill sdd-docs-dariomazzitellireplik-coder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-docs
Source: https://github.com/dariomazzitellireplik-coder/sdd-skills/tree/main/skills/sdd-docs
Command: npx skills add https://github.com/dariomazzitellireplik-coder/sdd-skills --skill sdd-docs-dariomazzitellireplik-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the updating of external documentation, such as CHANGELOG, README, and ADRs, after the code review phase is approved, reducing manual documentation work.

Core Features & Use Cases

Automated Documentation Update: Updates external documentation based on implemented changes.
Conditional Changes: Applies changes only if the review phase is approved.
Version Bumping: Optionally bumps version numbers for releaseable artifacts.
Use Case: After completing the code and review phases, this Skill can be used to update the project's documentation with the latest changes.

Quick Start

Run /sdd-docs to update documentation after the review phase is approved.

Frequently Asked Questions about sdd-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate documentation updates like CHANGELOG and README after a code review?▼

Automating documentation updates after code review requires parsing state.md and review.md to reflect implemented changes in external docs. This ensures CHANGELOG, README, and ADRs accurately capture the latest approved modifications.

What is the process for bumping version numbers in releaseable artifacts after approved changes?▼

Version bumping for releaseable artifacts is handled conditionally during the documentation update process. It triggers only after the code review phase is approved, ensuring version numbers reflect the newly implemented and reviewed changes.

How do I ensure my Architecture Decision Records update automatically when code changes?▼

To ensure Architecture Decision Records (ADRs) update automatically with code changes, you need an automated documentation tool that reads execution_plan.md and review.md. This applies conditional changes to ADRs only after the review phase is explicitly approved.

Can I update project documentation conditionally based on code review status?▼

Yes, you can update project documentation conditionally by checking the review.md file status. The documentation update process strictly applies changes to external docs only if the code review phase has been formally approved, preventing unreviewed modifications from being documented.

What files are required to automate change tracking for software documentation?▼

Automating change tracking for software documentation requires access to state.md, requirement.md, execution_plan.md, and review.md. These files provide the necessary context regarding implemented changes and approval status to update CHANGELOG and README accurately.