'comments' 검색 결과

Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.

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

Moves a person's whole Notion workspace into AI Matrx using only the AI Matrx and Notion connectors — every page and sub-page becomes an AI Matrx page (a Space) with its blocks, icons, covers, files and comments, and every database becomes a real table with typed columns, links, roll-ups, row pages, templates and views. Safe to run again; nothing duplicates. Use when the person says "move my Notion into AI Matrx", "copy my Notion", "import my Notion", or anything like it.

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

Bringing an existing table onto the platform base standard. Use when asked to canonicalize, retrofit, or 'Wave 3' a table, run apply_rls or an org backfill, retire a bespoke *_versions table, or move it onto platform comments/associations/permissions. NOT for a schema move (use db-move-table-schema).

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

Route a PR review request to the correct tool — code-review plugin (quick parallel scan across all dimensions) or pr-review-toolkit (deep-dive on a specific quality dimension such as type design, error handling, test quality, comments, or simplification). Use when the user asks for a code review, PR review, or mentions a specific quality concern before creating a PR.

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

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

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

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

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

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

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

Review code changes from current branch, an Azure DevOps PR, a git ref, or a diff/patch file. Trigger when user says "review this", "code review", "/df:code-review", or provides a PR id/URL, ticket URL, git ref, or diff path. Read-only — never posts comments.

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

Review code changes from the current branch, staged changes, a git ref, or a diff/patch file. Pure git-native — no platform/PR awareness. Trigger when user says "review this", "review diff", "/aiwork:code-review-diff", or provides a git ref or diff path. Read-only — never posts comments.

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

Azure DevOps pull requests, for repos whose git remote is on dev.azure.com or *.visualstudio.com. Covers comment threads, which `az repos pr` cannot read or post. Use to create a PR for the current branch, check out, list or complete PRs, post code comments on a PR, reply to threads, and assess whether review feedback was addressed. Trigger on "create PR", "checkout PR 123", "list PRs", "complete PR", "comment on the PR", "post these review findings", "check PR feedback", "/dev-azdo:pr".

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

Ensure that Java types are documented with Javadoc comments and follow best practices for documentation.

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

Ensure that C# types are documented with XML comments and follow best practices for documentation.

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

Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial.

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

Review PRs: diffs, inline comments via gh or REST.

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

Writes XML doc comments. Tags, inheritdoc, GenerateDocumentationFile, warning suppression.

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

Performs read-only GitHub issue or PR triage with evidence links. Use when analyzing public or repository GitHub issues/PRs without mutating labels, comments, branches, reviews, merges, or issue state.

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

Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".

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

Documents TypeScript code with JSDoc comments, generates API documentation, and creates type-safe documentation. Use when users request "JSDoc", "code documentation", "API docs", "TypeDoc", or "inline documentation".

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

Use when reviewer comments arrive and each one needs a tracked decision, when a revise and resubmit letter must map every comment to a manuscript change, or when contradictory reviewer demands need evidence-based, editor-facing framing.

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

Hunt HTML Injection — user-supplied input is rendered as raw HTML in the response without sanitisation, allowing an attacker to inject arbitrary HTML tags (but not necessarily JavaScript). Lower severity than XSS but enables phishing, UI manipulation, and credential harvesting via injected forms. Use when testing text-display surfaces (search results, profile fields, comments, error messages, feedback forms). For markup that executes JavaScript, escalate to hunt-xss.

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

Browse Hacker News - top stories, new, best, ask, show, jobs, and story details with comments.

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

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

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

This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.

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

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

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