skills.rest
FlavioCFOliveira
FlavioCFOliveiraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

doc-manager

Generate and synchronize Go CLI documentation from source and SPEC data.

1|Updated Mar 16, 2026
Search Tags:#automation#documentation#cli#readme#go#docs-generation#command-docs
One-click install
npx skills add https://github.com/FlavioCFOliveira/Groadmap --skill doc-manager-flaviocfoliveira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-manager
Source: https://github.com/FlavioCFOliveira/Groadmap/tree/main/.claude/skills/doc-manager
Command: npx skills add https://github.com/FlavioCFOliveira/Groadmap --skill doc-manager-flaviocfoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates documentation management for Go CLI projects, ensuring that README.md and per-command documentation stay synchronized with source code and specifications.

Core Features & Use Cases

  • Generate a comprehensive root README.md with an index of available commands.
  • Create and update per-command docs under DOCS/commands based on code structure and SPEC data.
  • Analyze internal/commands and SPEC/COMMANDS.md to extract commands, subcommands, arguments, and flags for accurate documentation.
  • Keep documentation in sync when commands, flags, or behavior change.

Quick Start

Ask me to generate or sync the Go CLI project documentation by analyzing the source code and SPEC data, then create a root README.md and per-command docs under DOCS/commands.

Frequently Asked Questions about doc-manager

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

FAQPage Schema
How do I automate Go CLI documentation generation from source code?▼

To automate Go CLI documentation, the Skill analyzes internal/commands and SPEC/COMMANDS.md to extract commands, subcommands, arguments, and flags, then outputs a root README.md and per-command docs under DOCS/commands.

What is the best way to keep README documentation in sync with Go CLI commands?▼

Keeping README documentation in sync with Go CLI commands involves analyzing source structures and specification files to detect changes in flags or arguments, then regenerating README.md and DOCS/commands/*.md files to accurately reflect the current codebase.

Does doc-manager require a SPEC/COMMANDS.md file to generate CLI docs?▼

Doc-manager requires a SPEC/COMMANDS.md file alongside the internal/commands source structure to accurately extract commands, subcommands, arguments, and flags for generating README.md and per-command documentation.

How do I generate per-command markdown docs for a Go CLI project?▼

Generate per-command markdown docs for a Go CLI project by analyzing the source code structure in internal/commands and specification data, which creates individual markdown files under the DOCS/commands directory with accurate command, argument, and flag details.

Can I update existing CLI command docs without overwriting manual additions in README.md?▼

Updating existing CLI command docs regenerates README.md and DOCS/commands/*.md based on source code and SPEC/COMMANDS.md, meaning manual additions outside the generated structure may be overwritten when synchronizing documentation with the current codebase.

Related Skills

Explore More Software Engineering Skills→
mhawthornemhawthorne
11

gza-spec-review

Validate spec file claims against the current codebase and project structure.

Community
Intermediate
sardine-aisardine-ai
7

tui-cli

Parse TypeScript code to update CLI, TUI, and project Markdown documentation.

Official
Advanced
constzzconstzz

golang-continuous-integration

Automate Golang CI/CD pipeline setup with GitHub Actions.

Community
Advanced
dt418dt418

Docs Pack

Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.

Community
Intermediate