Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
日本語の概要は準備中です。原文の説明を表示しています。
Add JSDoc comments to JavaScript or TypeScript functions that are missing documentation. Use when asked to document functions, add JSDoc, or improve code comments.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Identify the functions or methods that are missing JSDoc comments. If the user specified a file, focus on that file. Otherwise, focus on whatever code is currently being discussed.
For each undocumented function, write a JSDoc block following these rules:
Read the function signature to determine parameter names and infer types from usage context, TypeScript annotations, or surrounding code.
Write a concise @description (one line maximum) that explains what the function does. If the function name already makes this completely obvious (isAuthenticated, formatDate), skip the description line and let the @param and @returns tags carry the documentation.
Write one @param tag per parameter:
@param {string} name? suffix or bracket notation: @param {string} [name]Write @returns with the return type and a brief description of what is returned and under what conditions. If the function returns void or never returns a meaningful value, omit @returns.
Write @throws if the function throws an exception under documented conditions: @throws {TypeError} If name is not a string.
Do not add @author, @date, @version, or other lifecycle metadata — these are noisy and go stale quickly.
UserId, use UserId, not string.Print the function name as a heading, then the completed JSDoc block. If the function already has a JSDoc block that is incomplete, print the corrected version.
Example output format:
getUserById
/**
* Fetches a user record by its unique identifier.
* Returns null if no user with that ID exists.
*
* @param {string} id - The user's unique identifier.
* @returns {Promise<User | null>} The user record, or null if not found.
* @throws {DatabaseError} If the database connection fails.
*/
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
日本語の概要は準備中です。原文の説明を表示しています。
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
日本語の概要は準備中です。原文の説明を表示しています。
Create a git branch named after a GitHub issue.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
日本語の概要は準備中です。原文の説明を表示しています。
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
日本語の概要は準備中です。原文の説明を表示しています。