'changes' 검색 결과

Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.

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

Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.

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

Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations. Use when schema changes affect existing data.

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

Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.

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

docs (editable docs people share and comment on; the default for any document, named as a doc or not: a document, report, proposal, resume, cover letter, letter, contract, policy, form, template, worksheet, essay, handbook, guide, how-to, cheat sheet, SOP or other writing to keep, share, collaborate on, send, submit, print or sign; a doc exports to Word, PDF, Markdown or Google Docs, so needing a file to send, attach, upload, submit or print is no reason to pick Word, and a file nobody asked for is a doc, not Word; a plan, comparison, summary or notes asked in chat stays in chat; a pasted claude.ai artifact link may be a doc: check with docs tools first; Word or another file format named, tracked changes wanted, or a .docx to change or use as a template → that format's skill): making one → if no docs-connector instructions are in context, call its `guide` (topic.instructions) first; then create the doc (headings only, no body) before any search, file read or plan, even with files attached.

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

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of Microsoft Word Documents, such as 'Word doc', 'word document', '.docx', '.dotx', 'microsoft doc'. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, 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 deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers Claude's own dedicated document or page skill or connector, use that instead, even if they will email or print it. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.

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

Read this before the first Google Drive, Docs, Sheets or Slides connector call whenever the task creates or changes a Google file. Use this skill whenever the user wants to create or change a Google Doc, Sheet or Slides file in their Google Drive. Triggers include: a request that names Google Docs, Sheets, Slides or Drive and asks to make, edit, format, copy or rename a file; a docs.google.com link with a request to change that file, even a one-line fix or suggested edits; and any follow-up change to a Google file from earlier in the chat, even "change it" or "add a tab". Includes helper scripts for document positions, cell ranges and slide layout. However, if the user asks for a doc, deck or spreadsheet without naming Google, or gives a Google file only as source material for something new, use Claude's own output type instead. Do NOT use for read-only questions about a Google file, or for Word, Excel, PowerPoint or PDF files.

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

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

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

Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.

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

Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.

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

Edit EcoSIM PFT-parameter NetCDF files such as ecosim_pftpar_20260303.nc with the ParEditor class from applications/notebooks/scripts/ParamEditor.py. Use when asked to modify, scale, copy, compare, or delete PFT parameter records for a plant functional type (six-character pfts code such as gr3s43 or ndlf34), update microbe parameter NetCDF values, or maintain the JSONL change log that records past parameter changes. Never modify plant_trait.*.desc files; they are read-only references.

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

Edit PDFs with natural-language instructions using the nano-pdf CLI. Modify text, fix typos, update titles, and make content changes to specific pages without manual editing.

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

Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.

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

Give Hermes phone capabilities without core tool changes. Provision and persist a Twilio number, send and receive SMS/MMS, make direct calls, and place AI-driven outbound calls through Bland.ai or Vapi.

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

Review code changes by analyzing git diffs, leaving inline comments on PRs, and performing thorough pre-push review. Works with gh CLI or falls back to git + GitHub REST API via curl.

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

Full pull request lifecycle — create branches, commit changes, open PRs, monitor CI status, auto-fix failures, and merge. Works with gh CLI or falls back to git + GitHub REST API via curl.

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

Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).

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

Analyze blast radius before making code changes

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

Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"

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

Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

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

Implement exactly one SDD Composy task in the ready state with dependency preflight, TDD RED evidence, allowed paths, real verification commands, and the guarded transition to qa_required. Use when a ready task should be executed — 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'. Do NOT use for changes without an approved task (sdd-quick), for autonomous multi-stage correction (sdd-loop), or for QA, review, or verification.

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

Use when the user wants a code review of an explicit range or set of files — correctness, security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and rule citations — 'revisar os últimos commits', 'code review da feature X', 'review base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.

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

Use when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (feat-review).

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

Deliver a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.

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