Adds JSDoc/TSDoc comments to all public functions and types in a file
Scanned 6/1/2026
Install via CLI
Skills Directoryopenskills install berkcangumusisik/claude-code-practices---
name: jsdoc
description: Adds JSDoc/TSDoc comments to all public functions and types in a file
argument-hint: <file-path>
user-invocable: true
allowed-tools: Read Edit
effort: low
---
## Add JSDoc Comments
File: **$1**
1. Read the file. Identify all public functions, methods, types, and interfaces without JSDoc.
2. For each, write a JSDoc comment that includes:
- `@description` - what it does (one sentence)
- `@param` - each parameter with type and description
- `@returns` - return value description
- `@throws` - if it can throw, what and when
- `@example` - a short usage example for non-obvious functions
Follow TSDoc format (`/** */`) for TypeScript files.
3. Rules:
- Don't state the obvious: `// Gets the user` → write *why/when* to use it
- Private/internal functions: add a brief comment only if logic is non-obvious
- Don't add params that are self-explanatory single-letter generics
4. Apply all comments to the file.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
