gsd-docs-update

Generate and verify documentation against codebase metadata in monorepos.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-docs-update-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-docs-update
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-docs-update
Command: npx skills add https://github.com/rkz91/coco --skill gsd-docs-update-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps codebase documentation synchronized with actual code, reducing drift and manual toil.

Core Features & Use Cases

  • Automated doc generation from codebase and metadata
  • Verification mode to check accuracy against code
  • Works across monorepos with multiple doc types

Quick Start

Run the docs-update workflow to regenerate and verify documentation across the project.

Frequently Asked Questions about gsd-docs-update

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

FAQPage Schema
How do I automate documentation generation for a monorepo?

Automating documentation generation for a monorepo is handled by exploring the codebase with subagents to extract metadata and produce up-to-date docs. The workflow supports multiple doc types across multi-module projects to reduce manual toil and documentation drift.

What is codebase documentation verification and how does it work?

Codebase documentation verification is the process of checking generated docs against actual source code for accuracy. This Skill uses a verification mode to validate that documentation reflects the current repository state, ensuring synchronized and reliable project metadata.

Can I verify existing docs without regenerating the entire codebase documentation?

Verifying existing docs without regenerating everything is supported using the --verify-only flag. This mode checks your current documentation accuracy directly against the codebase metadata, skipping the full generation process to save time.

Does automated documentation maintenance work across multiple module types?

Automated documentation maintenance works across monorepos containing multiple module types and doc formats. It uses repository metadata to explore the codebase and generate synchronized documentation, making it suitable for complex multi-module project structures.

What is the best way to keep documentation synchronized with code changes?

Keeping documentation synchronized with code changes is best achieved by automating the generation and verification workflow. By exploring the codebase and validating outputs against the source, this process reduces manual toil and prevents documentation drift.

Why does my codebase documentation drift from the actual source code?

Codebase documentation drifts from source code due to manual updates failing to keep pace with rapid code changes. Automating the documentation update workflow with verification against the repository ensures generated docs remain accurate and synchronized.