cmd-documentation-docs

Detect documentation tooling configs and locate API schemas across repositories.

2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill cmd-documentation-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-documentation-docs
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/cmd-documentation-docs
Command: npx skills add https://github.com/jlaws/dotfiles --skill cmd-documentation-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation teams often struggle to quickly locate and compose accurate documentation assets, tooling references, and API specs across diverse repos.

Core Features & Use Cases

  • Detect documentation tooling configs (e.g., OpenAPI, MkDocs, Sphinx) and identify existing docs directories.
  • Surface API schemas, changelogs, and technical docs for rapid writing and updating.
  • Use Case: A developer wants a unified doc plan for a new feature, including API surface, docs layout, and changelog entry.

Quick Start

Provide a diagnostic of the project's docs tooling, sources, and API schemas.

Frequently Asked Questions about cmd-documentation-docs

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

FAQPage Schema
How do I locate API documentation and OpenAPI specs across multiple repositories?

To locate API documentation and OpenAPI specs, this tool scans your repositories to detect tooling configurations, identify docs directories, and surface API schemas. It provides a diagnostic of existing documentation assets for technical writing workflows.

What is the best way to discover existing documentation tooling like MkDocs or Sphinx in a project?

Discovering documentation tooling involves detecting configuration files for frameworks like MkDocs and Sphinx within your project. The tooling diagnostic identifies these setups to help you understand the current docs layout and technical writing environment.

Can I generate a unified doc plan that includes API schemas and changelogs for a new feature?

Yes, you can compose a unified doc plan by surfacing API schemas and changelogs. The tool locates these technical documentation assets across your repos, enabling rapid writing and updating for new feature documentation.

How do I identify where changelogs and technical docs are stored in my codebase?

Identifying where changelogs and technical docs are stored requires scanning repository directories for documentation sources. The tool surfaces these assets by locating docs directories and detecting configured documentation tooling.

Does this documentation discovery approach work without specific dependencies or components?

Yes, this documentation discovery approach works without specific dependencies or components. It operates by satisfying constraints to detect tooling configurations and locate docs directories directly across your repositories.