docs

Generate changelogs, READMEs, ADRs, and API docs from code changes and design decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nshonda/workstation-setup --skill docs-nshonda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/nshonda/workstation-setup/tree/main/claude/skills/docs
Command: npx skills add https://github.com/nshonda/workstation-setup --skill docs-nshonda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation is often inconsistent and scattered across projects, making it hard to understand changes, decisions, and setup instructions.

Core Features & Use Cases

  • Generates changelogs, READMEs, ADRs, and API docs from code changes, decisions, and design notes.
  • Enforces routing and formatting standards across documentation artifacts to ensure consistency.
  • Useful for teams that need clear release notes, architecture decisions, and onboarding docs.

Quick Start

Write the right kind of doc, in the right place, in the right format.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I generate a changelog from code changes?

You generate a changelog from code changes by processing commit history and design decisions to produce standardized release notes. This documentation approach enforces consistent structure and routing across software project artifacts.

What is the best way to standardize project documentation across multiple repositories?

Standardizing project documentation requires enforcing formatting guidelines and routing standards across all artifacts. Generating READMEs and API docs from code changes ensures consistent structure and quick-start instruction support across software projects.

How do I write an Architecture Decision Record for software changes?

Writing an Architecture Decision Record involves capturing design decisions and routing them into a standardized project docs format. This ensures technical docs and code comments maintain consistent structure alongside changelogs and API documentation.

Does this documentation generation approach work for API docs and release notes?

Yes, documentation generation applies to API docs and release notes by extracting information from code changes and design notes. It enforces formatting standards to ensure consistent structure and routing across all project documentation artifacts.

Can I automate README creation from code changes and design notes?

You can automate README creation by extracting setup instructions and project context from code changes and design decisions. This enforces consistent structure and routing standards to standardize project documentation and onboarding materials.

When do I need structured documentation routing for software projects?

Structured documentation routing is needed when project documentation becomes inconsistent and scattered across teams. Enforcing routing and formatting standards ensures changelogs, ADRs, and API docs maintain consistent structure and location.