code-documentation

Enforce language-specific documentation standards across multi-language codebases.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill code-documentation-vivekmano27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-documentation
Source: https://github.com/Vivekmano27/agent-orchestrator/tree/main/plugins/project-orchestrator/skills/code-documentation
Command: npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill code-documentation-vivekmano27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate enforcement of consistent inline documentation across multi-language codebases to improve maintainability and onboarding.

Core Features & Use Cases

  • Public APIs must be documented using language-specific doc formats (JSDoc/TSDoc for JavaScript/TypeScript, Google-style docstrings for Python, KDoc for Kotlin, and dartdoc/godoc equivalents for Dart and Go).
  • Private/internal code should be documented when the logic is non-obvious or has side effects; TODO/FIXME must reference tickets.
  • Provides a centralized standard used during feature development and code reviews to raise documentation quality across teams.

Quick Start

Review new or modified code and apply the project’s documentation standards to all public APIs and complex internal logic.

Frequently Asked Questions about code-documentation

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

FAQPage Schema
How do I enforce consistent code documentation standards across multiple programming languages?

Enforce consistent code documentation by applying language-specific formats like JSDoc for JavaScript and Google-style docstrings for Python during feature work and code reviews, ensuring standardized inline documentation across multi-language codebases.

What is the standard for writing TODO and FIXME markers in a multi-language codebase?

TODO and FIXME markers must reference mandatory tickets to maintain traceability. This standard applies across all supported languages, ensuring that technical debt and pending tasks are properly tracked during code reviews.

How do I document private internal code when the logic is non-obvious?

Document private internal code when the logic is non-obvious or has side effects. Apply the relevant language-specific doc format such as KDoc for Kotlin or TSDoc for TypeScript to clarify complex behavior and improve maintainability.

Does this documentation standard support Python and Kotlin public APIs?

Yes, the standard supports Python and Kotlin public APIs. It requires applying Google-style docstrings for Python and KDoc for Kotlin, ensuring that all public interfaces across the multi-language codebase are consistently documented.

What is the best way to automate inline documentation checks during code reviews?

Automate inline documentation checks by integrating a centralized documentation standard into your code review workflow. This enforces language-specific doc formats and frontmatter-driven metadata for all new or modified code.

When should I use dartdoc and godoc formats for my codebase?

Use dartdoc for Dart and godoc for Go when documenting public APIs and complex internal logic. These language-specific formats are mandated by the standard to ensure consistent documentation quality across multi-language codebases.