documentation

Add missing JSDoc, module-level comments, and @returns tags to codebases.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/gil00pita/lanify --skill documentation-gil00pita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation
Source: https://github.com/gil00pita/lanify/tree/main/.agents/skills/documentation
Command: npx skills add https://github.com/gil00pita/lanify --skill documentation-gil00pita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation gaps in codebases slow onboarding, obscure intent, and reduce maintainability. This skill targets missing JSDoc, absent module-level documentation, and missing @returns tags across functions and modules.

Core Features & Use Cases

  • Identify missing or incomplete JSDoc on exported functions and modules.
  • Add concise, purposeful documentation that explains intent, edge cases, inputs, outputs, and side effects.
  • Use during code reviews, PRs, and onboarding to improve code understanding and maintainability.

Quick Start

Identify a function with insufficient documentation and generate a concise JSDoc block including a description, parameter descriptions, and a returns section.

Frequently Asked Questions about documentation

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

FAQPage Schema
How do I add missing JSDoc comments to functions during a code review?

To add missing JSDoc during code reviews, generate concise blocks containing descriptions, parameter details, and @returns tags for exported functions and modules. This ensures intent, inputs, outputs, and edge cases are clearly documented for maintainability.

What is the best way to document module-level comments and edge cases in JavaScript?

Documenting module-level comments and edge cases involves adding concise documentation that explains module intent, side effects, and specific edge-case guidance. This practice clarifies usage and reduces onboarding friction for new developers.

Does this documentation approach work with ESLint-jsdoc standards?

Yes, this documentation approach integrates with ESLint-jsdoc standards. It meets requirements for module docs, param descriptions, and return values, ensuring generated JSDoc blocks comply with standard linting rules during PRs and onboarding.

Why does missing @returns tag documentation reduce code maintainability?

Missing @returns tags reduce code maintainability because return values become obscured. Adding these tags alongside parameter descriptions and module-level comments clarifies function outputs, preventing misuse and easing developer onboarding.

Can I automatically fix incomplete JSDoc on exported functions without manual writing?

Yes, you can fix incomplete JSDoc on exported functions automatically by identifying missing blocks and generating purposeful descriptions, parameter details, and return values. This ensures every function has clear usage and edge-case guidance without manual writing.