gsd-docs-update

Name: gsd-docs-update
Availability: InStock
Author: dobrinz123

Generate and update codebase-verified project documentation with --force and --verify-only flags.

Updated Apr 9, 2026

Search Tags:#automation #documentation #codebase #verification #gsd #doc-generation

Ready to run

npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-docs-update-dobrinz123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-docs-update
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-docs-update
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-docs-update-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate and update project documentation that is accurate to the current codebase, eliminating stale, hand-edited docs and reducing manual verification effort.

Core Features & Use Cases

Code-verified doc generation: Spawns gsd-doc-writer subagents that explore the repository to produce documentation without inventing paths or signatures.
Selective regeneration and verification: Honors literal flags such as --force to overwrite or --verify-only to check existing docs without writing.
Preservation and reporting workflow: Preserves workflow gates, supports monorepos and multi-file dispatch, commits changes, and produces verification reports for auditability.

Quick Start

Ask the agent to run gsd-docs-update with the --verify-only flag to check existing documentation against the codebase without writing files.

Frequently Asked Questions about gsd-docs-update

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

FAQPage Schema

How do I generate project documentation that matches my current codebase?▼

Project documentation matching your live codebase is generated by spawning subagent writers that explore the repository and produce docs without inventing paths or signatures. This ensures your documentation accurately reflects your actual source files.

Can I verify existing documentation against the source code without overwriting it?▼

Yes, you can verify existing documentation without overwriting by running the update process with the literal --verify-only flag. This checks your current docs against the codebase and reports results without writing any changes to files.

What's the best way to update stale docs across a monorepo?▼

Updating stale docs across a monorepo is handled through multi-file dispatch and selective regeneration. The workflow reads the repository with file-level inspection and preserves workflow gates while regenerating documentation across multiple project packages.

Does codebase documentation generation work with per-file preservation and workflow gates?▼

Codebase documentation generation supports per-file preservation and honors workflow gates during the update process. It reads the repository, runs subagent writers, and writes or reports results while maintaining your existing repository validation rules.

How do I force overwrite outdated documentation files in my repository?▼

To force overwrite outdated documentation files, use the literal --force flag when running the documentation update. This bypasses preservation and overwrites existing docs with newly generated, code-verified content.

Why does manually edited documentation become stale and inaccurate over time?▼

Manually edited documentation becomes stale because it relies on human updates rather than codebase verification. Automated doc generation eliminates this by reading live source files and verifying signatures and paths to ensure ongoing accuracy.