Documenter Skill

Update README, code comments, Arc42 specs, examples, and CHANGELOG after code changes.

4|1|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/deMGoncalves/arq-specs-template --skill documenter-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Documenter Skill
Source: https://github.com/deMGoncalves/arq-specs-template/tree/main/.claude/skills/documenter
Command: npx skills add https://github.com/deMGoncalves/arq-specs-template --skill documenter-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all project documentation—from README.md to API references and CHANGELOG.md—is consistently updated and synchronized with the latest code changes. It automates the often-overlooked task of documentation, preventing outdated or missing information.

Core Features & Use Cases

  • Comprehensive Documentation Updates: Automatically updates various documentation artifacts, including README.md, CHANGELOG.md, API documentation, and code comments, reflecting new features, bug fixes, and refactorings.
  • Specification Synchronization: Ensures that specs/ documents (e.g., Arc42 views, BDD scenarios) are aligned with the implemented code, maintaining a single source of truth.
  • Doc Comment Generation: Generates or updates doc comments for public APIs, functions, and modules, improving code readability and maintainability.
  • Use Case: After a new feature is implemented and reviewed, this Skill automatically updates the README.md with usage instructions, adds an entry to CHANGELOG.md, and ensures all relevant specs/ are synchronized, saving developers from manual documentation tasks.

Quick Start

After code review is complete, invoke the Documenter to update all relevant documentation: @skill documenter

Frequently Asked Questions about Documenter Skill

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

FAQPage Schema
How do I automate documentation updates when code changes?

Automate documentation updates by invoking the Documenter Skill after code review is complete. It synchronizes README, CHANGELOG, API docs, code comments, and architectural specs (Arc42 templates) with your latest implementation, eliminating manual documentation tasks and keeping specs in sync with code.

What documentation artifacts can be automatically updated?

The Documenter updates README.md, CHANGELOG.md, API documentation, code comments, architectural specifications in specs/ directories (including Arc42 views), BDD scenarios, and ADRs. It maintains terminology consistency, adds cross-references, and tracks last-updated metadata across all documentation types.

Can I keep my specs synchronized with implementation changes?

Yes. The Documenter ensures specs/ documents remain aligned with implemented code by consulting reference templates, following template structure, maintaining status metadata, and generating cross-references and ADR updates when code approvals necessitate documentation changes.

When should I use automated documentation synchronization?

Invoke automated documentation synchronization after code review approval to prevent outdated or missing information. It's critical for multi-artifact projects where README, CHANGELOG, API references, and architectural specs must reflect new features, bug fixes, and refactorings simultaneously.

How do doc comments improve code maintainability?

Doc comment generation automatically documents public APIs, functions, and modules with WHY context in code comments, improving readability and maintainability. The Documenter links comments to source implementation and ensures documentation describes intent, not just what the code does.

Do I need templates for consistent specification updates?

Yes. The Documenter consults reference templates before updating specs and follows template structure to maintain consistency. It works with Arc42 templates and other structured formats to ensure all specifications follow a single source of truth pattern.