add-docs

Add inline documentation comments to undocumented public symbols in source files across a repository.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill add-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-docs
Source: https://github.com/mattbobambrose/mattbobambrose-claude-skills/tree/main/plugins/documentation/skills/add-docs
Command: npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill add-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many codebases lack clear inline documentation for public symbols, making it hard for new contributors and maintainers to understand APIs quickly. This Skill automates detection of undocumented public functions, methods, classes, and constants and assists in adding concise, idiomatic doc comments without overwriting existing documentation.

Core Features & Use Cases

  • Language-aware doc generation: Detects comment styles for Kotlin/Java (KDoc), TypeScript/JavaScript (JSDoc), Python (Google-style docstrings), Go, and Rust and generates appropriate comment blocks.
  • Safe, review-first edits: Reads files, lists undocumented symbols, prompts for confirmation before editing, and preserves any existing comments.
  • Reporting and flagging: Produces a summary of files changed, counts of comments added, and marks symbols that are unclear and require human clarification.

Quick Start

Add inline doc comments to all undocumented public symbols under src/ and show a confirmation prompt before making any edits.

Frequently Asked Questions about add-docs

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

FAQPage Schema
How do I automatically generate inline documentation for undocumented public APIs?

Automatically generate inline documentation by scanning source files to discover public functions, methods, classes, and constants missing comments. It detects language-specific styles, proposes concise doc comments, and requires explicit user confirmation before applying any edits to preserve existing documentation.

Does auto-documentation work with Python docstrings and TypeScript JSDoc?

Auto-documentation works with Python Google-style docstrings, TypeScript and JavaScript JSDoc, Kotlin and Java KDoc, Go, and Rust. It detects the appropriate language-specific comment style and generates idiomatic documentation blocks for each detected public symbol.

Can I scan an entire repository for missing code documentation?

Scan an entire repository, a specified directory, or a single file to find undocumented public symbols. The tool reads the target path, lists discovered functions and constants lacking comments, and presents a summary for review before making any changes.

How does safe auto-documentation handle existing comments in source files?

Safe auto-documentation preserves existing comments by only targeting undocumented public symbols. It reads your files, identifies what is missing, and prompts for explicit confirmation before editing, ensuring no original documentation is overwritten during the generation process.

What happens when code is too unclear for automatic docstring generation?

When code is too unclear for automatic docstring generation, the tool flags those specific symbols for manual review. It produces a summary report of files changed, counts of comments added, and clearly marks ambiguous symbols requiring human clarification.

What is the best way to add concise inline docs to public functions across a codebase?

The best way to add inline docs is to apply an automated tool that detects missing comments across common programming languages. It generates concise, idiomatic documentation blocks for public APIs and provides a confirmation prompt to review changes before committing edits.