Docs Code

Analyze a codebase, get confirmation on the module map, then make every comment high-value — add, modify, or delete as needed, including cleaning experimental comments — without changing code behavior.

When NOT to Use

• The goal is simplifying or refactoring code: use clean-code instead. This skill only changes comments, never code logic.
• The goal is deleting unused code: use fire instead.
• The goal is documentation beyond code comments (README, guides, tutorials): use write-docs instead.

Trigger Scope

Pick one path based on how the skill was triggered:

1. full pass (default when the user asks to document a codebase, directory, or module): run all phases below, including confirmations.
2. inline annotation (when triggered proactively — e.g., the agent is about to write a comment — or the target is a single file, function, or small comment change): skip Phase 0 and Phase 1. Apply Comment Quality Rules, Comment Style, What to Add, and Large File Rules directly. When modifying or deleting comments, keep only those that pass the Comment Quality Rules. Then run Phase 3 verification on the changed scope.

Phase 0: Execution Mode