스킬 찾기

Review a change for security defects such as secret exposure, injection, authentication/authorization failures, unsafe deserialization, and dependency risk. Use for an independent security perspective on a defined change set.

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

Load the shared verdict, punch-list, SKIP, and gate schema used by the dh multi-perspective review orchestrator, reviewers, and synthesizer. Use only when one of those components must produce, parse, validate, or gate review results.

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

Trace bugs, CI failures, and unexpected behavior from reproduced evidence to a causal mechanism and governing contract. Distinguish product, architecture, test-oracle, and harness defects; investigate intermittent failures with controlled experiments and report unresolved evidence explicitly.

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

Works backward from the stated goal through its prerequisite chain — what must exist to reach the goal, then what each of those requires, back to the current state — classifying each prerequisite as AVAILABLE, DERIVABLE, or MISSING, and blocking planning until nothing is MISSING. Use before creating plans, delegating to agents, or defining acceptance criteria. Activates on specs, PRDs, tickets, RFCs, architecture designs, and multi-step engineering tasks. Always pass `#N` or an inline goal — invoking with no argument and no inline context returns BLOCKED. Integrates with CoVe-style planning pipelines.

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

Use when executing a task — reads the task and its orchestrator response from the work ledger, loads task-level skills, and implements against acceptance criteria. A dispatch-owned attempt records divergences and the completion report, then closes; a direct invocation returns its task result and material divergence disposition without runner persistence or closure. Triggers on task execution within the implement-feature loop or when an agent picks up a specific task from a plan.

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

Decomposes a contextualized plan into atomic, independently executable tasks with complete embedded context, registered through the plan API. Use after SAM Stage 3 Context Integration produces the contextualized plan artifact — when the plan is ready for task generation with CLEAR ordering, CoVe checks, and dependency graphs for parallel execution.

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

Use when investigating failing tests or deciding whether to change the test or product. Validate test expectations against authoritative intent, trace product and test boundaries, and require evidence for the correction rather than automatic code fixes or test dismissal.

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

Review existing tests against the software and contracts they actually exercise. Use to assess whether a test has justified unique protection, detects consequential faults, tolerates valid refactors, earns its lifecycle cost, or deserves strengthening, replacement, consolidation, or removal consideration. Reviews are read-only and evidence-backed, including TDD and regression tests.

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

Executes a groomed milestone with parallel kage-bunshin sessions in isolated worktrees. Use when a milestone has been groomed and /groom-milestone has produced a dispatch plan. Reads the dispatch plan, creates an integration branch, spawns one kage-bunshin (independent claude -p process) per wave item in its own worktree — each session is a full orchestrator with the Agent tool. Sequentially merges worktree branches, relays wave discoveries to subsequent waves, then lands the integration branch to main. Takes a milestone number as argument.

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

Query and invoke tools on MCP servers using fastmcp list and fastmcp call. Use when you need to discover what tools a server offers, call tools, or integrate MCP servers into workflows.

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

Use when designing or validating GitLab CI/CD and automatic release lifecycles, inspecting pipeline and job state read-only, composing non-interactive merge-request commands, or setting up protected refs and release credentials. Also covers reusable components and inputs, GitLab Functions, gitlab-ci-local, glab command composition, and GitLab Flavored Markdown. For pipeline execution or retry requests, provide inspection and command drafting while leaving execution to the operator.

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

When setting up local LLM inference without cloud APIs. When running GGUF models locally. When needing OpenAI-compatible API from a local model. When building offline/air-gapped AI tools. When troubleshooting local LLM server connections.

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

This skill should be used when the user asks to "write a Perl script", "create Perl code", "modern Perl best practices", "Perl 5.30+", "use strict warnings autodie", or mentions Perl pragmas, subroutines, error handling, or scripting patterns. Provides comprehensive Perl 5.30+ development guidance.

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

This skill should be used when the user asks to "install perlbrew", "set up Perl environment", "install Perl version", "manage Perl versions", "switch Perl version", "install plenv", or mentions Perl version management, development environment setup, or multiple Perl installations.

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

This skill should be used when the user asks to write Perl tests, test Perl code, use Test More, run prove, create test suite, mock Perl, or mentions Perl testing, TAP, Test Class, Test Deep, or test-driven development in Perl.

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

This skill should be used when the user asks to lint Perl code, run perlcritic, check Perl style, format Perl code, run perltidy, or mentions Perl Critic policies, code formatting, or style checking.

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

Routes a Superpowers plan file through the /work-backlog-item pipeline and writes SAM task back-references and chunk annotations into the original plan. Use when given a path to a Superpowers plan file via $ARGUMENTS and needing to create a linked backlog item plus SAM task plan.

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

Same reverse-thinking method as dh:rt-ica (see dh:rt-ica or dh-glossary for the definition), but localizes any MISSING input to the affected task only, as a non-blocking information-completeness pre-pass before task decomposition and plan generation. Use when grooming backlog items, generating plans, decomposing tasks under uncertainty, or working in brownfield and refactor scenarios. Produces completeness summary (APPROVED-FOR-PLANNING, APPROVED-WITH-GAPS, or BLOCKED-FOR-PLANNING), missing input report with dependency mapping, required unblock actions, and planning annotations for downstream tasks. Use dh:rt-ica instead at the S2 implementation gate where missing inputs must halt execution.

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

Review a code change for correctness-maintainability defects not owned by a narrower security/performance/accessibility perspective. Use for an independent quality perspective on a defined change set.

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

Use when creating or updating the project skill discovery config — generates or regenerates .dh/skill_discovery.yaml by scanning the repo to infer tech stack, inventorying installed skills via npx skills list, loading candidate skill content before suggesting, and writing a config-driven skill injection file. Triggers on /dh:setup-skill-discovery invocations and programmatic --auto calls from add-new-feature Phase 3.

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

Synchronize existing documentation with an observed code/configuration/API change while preserving each document's purpose and authority. Use after implementation changes can make documentation stale, incomplete, or internally inconsistent.

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

Synthesize multiple independent structured review verdicts into one lossless deduplicated punch list. Use when findings from several review perspectives must be merged without inventing, dropping, or changing source verdicts.

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

Design validation and maintained regression protection before test authoring. Use for TDD increments, acceptance or regression evidence, test boundary/oracle decisions, and multi-factor interaction coverage.

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

Scientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, refactoring, or implementation is complete — enforces reproduce-broken-state then define-success-criteria then apply-fix then verify-outcome. Success means observing intended behavior, not absence of errors.

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