cc-docs

Generate and synchronize README, CHANGELOG, API docs, and CLAUDE.md with code changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation drift is common after shipping features; this skill automates generation and synchronization of README, CHANGELOG, API docs, and CLAUDE.md to keep project docs aligned with code.

Core Features & Use Cases

  • Generates and maintains README.md, CHANGELOG.md, API docs, and CLAUDE.md.
  • Keeps documentation in sync with code changes across releases and PRs.
  • Useful for post-release workflows, feature stabilization, and ongoing maintenance.

Quick Start

Run the documentation workflow after a release to refresh all documentation artifacts.

Frequently Asked Questions about cc-docs

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

FAQPage Schema
How do I keep project documentation in sync with code changes after a release?▼

To keep documentation in sync with code changes, you can automate the generation and synchronization of README.md, CHANGELOG.md, and API docs during post-release workflows. This prevents documentation drift by applying updates directly from code state and release notes.

What is the best way to automatically generate a Keep a Changelog style file?▼

The best way to generate a Keep a Changelog style file is to use a documentation workflow that enforces this specific format automatically. It synchronizes your changelog with code state and release notes, ensuring consistent logging of changes across feature merges.

How do I update API docs and CLAUDE.md files during ongoing maintenance?▼

You can update API docs and CLAUDE.md files during ongoing maintenance by running an automated documentation synchronization workflow. This process refreshes these artifacts based on the latest code changes and frontmatter-driven templates.

Does this documentation synchronization workflow support custom templates?▼

Yes, the documentation synchronization workflow supports frontmatter-driven templates. This allows you to maintain customized structures for your README.md, API docs, and CLAUDE.md files while keeping the content aligned with your codebase.

When should I run the project documentation generation workflow?▼

You should run the documentation generation workflow after a release, during feature merges, or as part of ongoing maintenance. Applying it to these post-release workflows ensures all documentation artifacts reflect the current code state.

Can I use this to prevent documentation drift across feature stabilization?▼

Yes, you can prevent documentation drift across feature stabilization by automating synchronization of README.md, CHANGELOG.md, and API docs. It applies code state changes to documentation continuously, ensuring alignment throughout the stabilization process.