'changes' 검색 결과

Use when implementing a new function, adding a feature, fixing a bug, refactoring with test coverage, or writing a new test. Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predict-the-failure-before-every-run checks, hardcode-first minimum changes, triangulation, and property-based testing for large input spaces. Triggers on explicit TDD requests and on any task phrased as "implement", "add", "write a function", "build a feature", or "fix a bug" in a test-capable codebase. Reports red/green validation evidence.

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

Generate a bullet-point summary of branch changes for a PR description. Triggers on "changelog", "pr summary", "summarize branch", or "/changelog".

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

Check any artifact against an explicit specification and report adherence using the add-comments workspace format. Use when validating plans, scripts, docs, or code changes against a source-of-truth spec.

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

Boss delegates tasks to workers, reviews their output, and approves or requests changes.

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

Keep inherited changes narrow, correctly marked, traceable, and easy to rebase across repository layers.

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

Use this Canvas-owned clean-room skill for creating, reading, editing, reviewing, redlining, commenting, or repairing Word `.docx` documents. Trigger for Word documents, DOCX files, memos, reports, letters, templates, tracked changes, comments, table of contents, headers, footers, page numbers, and Google Docs-targeted documents that should be authored as DOCX first.

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

Load this skill immediately whenever a project contains an ACCESSIBILITY.md file, or whenever you are contributing to the mgifford/ACCESSIBILITY.md repository. Absolutely always read ACCESSIBILITY.md before proposing or writing any changes. Under no circumstances skip this skill when an ACCESSIBILITY.md file is present. This skill governs when and how all other accessibility topic skills must be loaded.

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

Development methodology rules (Clean Architecture, TDD flow, 3-Strike rule, decision priority) that govern planning, implementation, and review. Load before designing, staging, implementing, or reviewing code changes.

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

Visual expression system for AI personas with emotion-based face switching. Use at session start to display the expression UI, and switch expressions whenever the emotional state changes during conversation.

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

Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx skills—not domain app tutorials.

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

Record browser or Web UI interaction demos as optimized GIFs using the available built-in browser, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and model flow.

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

Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website/docs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content changes.

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

Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM message receive, reactions, chat member changes, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.

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

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', 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 or .dotx 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.

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

Design and review client UI changes — visual token discipline, reuse-before-adding, feedback surfaces (toast vs in-place notice vs empty state), overlay and menu safety, platform window adaptation, loading states, and error copy placement. Use when adding or changing product-user-visible GUI behavior, or when reviewing such a PR.

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

GStack retrospective method for completed workstreams, identifying what worked, what failed, process changes, and role-skill improvements.

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

GStack unfreeze method for safely resuming a previously frozen task with explicit resume criteria, allowed changes, and verification gates.

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

Systematic testing methodology for exhaustive branch coverage, edge case identification, and production bug prevention. Use when PR review reveals incomplete test coverage, when tests pass but users report bugs, when code changes break existing features, when verifying all branches and edge cases before merge, when analyzing "it works on my machine" issues, when planning test strategy for new features, or when debugging flaky tests and race conditions.

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

Find and eliminate technical debt across the whole codebase — duplicated code, dead code, redundant abstractions. Use at the end of a coding session or when the codebase feels bloated. Reports findings and fixes them with user confirmation. Cleanups limited to the current working changes belong in a native simplify flow instead.

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

After any correction from the user, update CLAUDE.md with a rule to prevent the same mistake from recurring. Use when the user corrects your behavior or says "don't do that again". Writes durable instruction-file rules — for machine-enforced behavior, prefer a hook-writing skill (e.g. hookify) or settings changes when available.

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

You are a documentation engineer. Detect code changes, update corresponding docs, remove stale references, validate quality.

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

Use this skill when the company is about to buy, renew or switch on an AI product or an AI feature inside an existing product, and asks "assess this AI vendor", "do they train on our data", "AI supplier questionnaire", "review the AI terms", "can we use this model provider with customer data", "who are the subprocessors behind this AI tool" or "AI vendor risk assessment". Sizes the review to the use, reads the terms, data processing agreement and documentation before asking questions, checks training use, retention, model changes, subprocessors, transfers, security and exit, and writes an assessment with a recommendation plus the follow-up questions for the vendor.

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

Use this skill when the periodic policy review is due or overdue, or someone asks "run the annual policy review", "our policies are out of date", "re-approve the policies before the audit", "what changed since the last review", "policy version history" or "who needs to sign off which policy". Collects what changed since each policy was last approved (incidents, findings, exceptions, new systems, law), proposes the edits per policy, separates editorial from substantive changes, drafts the version history and approval record, and plans the communication to staff.

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

Use this skill when an external audit, attestation examination or assessment is coming and the team wants populations and evidence ready for the samples the auditor will pull, or asks "prepare for audit sampling", "what samples will the auditor ask for", "get our populations ready", "the auditor wants a list of all changes in the period", "evidence for the leavers sample", "Type II sample prep" or "how do we prove completeness of the population". Lists the populations an auditor is likely to sample, builds each from the system of record with the query that produced it, checks completeness and the evidence behind a dry-run sample, and writes a readiness file per population plus a list of gaps to fix before fieldwork.

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