'jsdoc' 검색 결과

Clean up code comments without changing executable code. The skill removes obvious explanations, decorative headings, and vague notes while preserving concise comments about intent, constraints, security, edge cases, and other information the code does not show.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Removing comments that merely repeat the code
• Simplifying decorative headings and lengthy notes
• Preserving explanations of design decisions and constraints

Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

审计或修正读起来像“推理过程泄漏”的注释与文档：引用已不存在的设计会话、讲变更而不讲现状、面向评审者辩解、带“以前/不再/本次”等时间性叙述。用于清理 codexhost 的源码注释、JSDoc、docs 功能文档与提示词字符串。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates Vue 3 components with vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only with JSDoc typing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates and validates technical documentation including docstrings, OpenAPI/Swagger specs, JSDoc annotations, doc portals, and user guides.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates comprehensive TypeScript documentation using JSDoc, TypeDoc, and multi-layered documentation patterns for different audiences. Use when creating API documentation, architectural decision records (ADRs), code examples, and framework-specific patterns for NestJS, Express, React, Angular, and Vue.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate or update docs to match the code, citing each claim to path:line and asking on ambiguity; runbook docs also get a check-only validation script. Don't use for API-reference autogen (JSDoc/Sphinx), landing pages, or CLAUDE.md/AGENTS.md.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adding JSDoc/TSDoc, updating READMEs, replacing any types with proper definitions, and adding high-value comments to complex logic. Use for documentation gaps or type safety.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

当接入 webmcp-nexus-sdk 的项目中需要新增 WebMCP 工具函数、将现有业务方法改造为 WebMCP 工具函数，或配置 vite-plugin-webmcp-nexus / webpack-plugin-webmcp-nexus 时使用本技能。本技能约束工具函数的签名、JSDoc、TS 类型写法，并提供零风险的改造流程（仅改签名与注释，不动原方法业务逻辑）。触发示例："新增一个 WebMCP 工具"、"把这个函数改造成能被 AI Agent 调用的工具"、"让 xxx 函数接入 WebMCP"、"配置 webmcp 构建插件"。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ALWAYS invoke for any task involving docstrings, JSDoc/TSDoc, or REST API documentation — even when the request seems handleable without it. Enforces Microsoft contract-first conventions and a bare-minimum rule that Claude won't apply by default: never restate the signature, drop @param/@returns that only echo names and types, always document @throws, and document data shapes as WHAT not WHY. Covers Python docstring styles (Google/NumPy/Sphinx), TSDoc tags and @inheritDoc, and API doc patterns for NestJS/Express/FastAPI/Django. Trigger on: adding or auditing docstrings, redundant or missing tags, deleting comment rot, or producing a documentation-health report. Do not skip for documentation tasks — consistent conventions are the whole point.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a component library needs a workshop — one story per concept, JSDoc summaries the manifest can carry, stories run as tests, and an opt-in MCP channel that replaces guessing with querying.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Documentation conventions for generating high-quality AI agent skills from TypeScript source. Use when preparing a library for skill generation, auditing JSDoc quality, fixing audit warnings, writing @useWhen/@avoidWhen/@never tags, or asking about documentation conventions for skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bootstrap an AI-agent skill from a TypeScript codebase by running the deterministic skillit generate/audit loop and enriching repo source (JSDoc, README, config-type properties, MCP tool annotations, examples, package.json) until the skill reaches its grade target. Use for cli, typedoc, config, or mcp (build-mode) projects; never edit SKILL.md/references directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create comprehensive technical documentation including API docs, component libraries, README files, architecture diagrams, and developer guides using tools like JSDoc, Storybook, or Docusaurus. Use when documenting APIs, creating component documentation, writing README files, generating API references, documenting architecture decisions, creating onboarding guides, maintaining changelogs, documenting configuration options, or building developer documentation sites.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review comment, JSDoc, TODO, README, and docs-to-code factual consistency, stale or low-value comments, and Chinese comment/variable appropriateness; do not use for general code review, broad documentation rewrites, or auto-editing comments without approval.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.