2.1천건 · 관련도순
Plan and execute Azure deployments safely and repeatably for applications and infrastructure. Use this skill when users ask to deploy, publish, release, or provision workloads in Azure. Covers Infrastructure-as-Code, idempotency, health validation, and rollback strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build production CI/CD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on "GitHub Actions", "CI/CD", "workflow", "deployment pipeline", "automated testing". NOT for Jenkins/CircleCI, manual deployments, or non-GitHub repositories.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Blue-green and canary deployment orchestrator with traffic shifting and automated rollback. Activate on: blue-green deployment, canary release, rolling deployment, traffic shifting, rollback automation, progressive delivery, Argo Rollouts, Flagger. NOT for: K8s manifest generation (use kubernetes-manifest-generator), CI/CD pipeline setup (use github-actions-pipeline-builder), monitoring (use monitoring-stack-deployer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keep module structure, naming, and build configuration ready for future publishing. Handle new Gradle modules, library metadata, namespace and artifact readiness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Auto-activate for uv build, hatch build, PyApp, PYAPP_*, wheel assets, GitHub release matrices, cargo-zigbuild, or python-build-standalone. Not for runtime deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare GEODE worktrees, Korean PRs, CI-gated merges, and guarded cleanup. Use for repository branch, commit, PR, merge, or release work; apply only the stages the user authorized.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GEODE runtime context for model selection and metadata, architecture, packaging, release, docs, CI, AgenticLoop, async runtime, and plugin boundaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply GEODE's measured architecture, module and symbol naming, Python type/class, persisted schema, test, site, and versioning conventions. Use when adding or moving modules, choosing dataclass/Pydantic/Protocol/ABC forms, naming classes or files, designing stored data, reviewing convention compliance, or deciding compatibility and release version treatment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Actualiza CHANGELOG.md en el formato Keep a Changelog, añadiendo los cambios actuales bajo la sección Unreleased. Úsalo cuando la persona pida actualizar el changelog, añadir una entrada al changelog o registrar lo que cambió para las notas de la versión (p. ej. "añade esto al changelog", "actualiza el CHANGELOG con estos commits").
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query the Ensembl REST API for gene/transcript/protein lookup, sequence retrieval, comparative genomics (Compara), variant effect prediction (VEP), regulatory features, and cross-species ortholog/paralog calls. Use when pulling Ensembl-native data (Ensembl Gene IDs, version-pinned releases, archive endpoints for reproducibility), gene/transcript/exon structure with stable IDs, or VEP for variant annotation. Encodes the 15 req/sec rate limit, archive (e110.rest.ensembl.org) for reproducibility, Ensembl divisions (vertebrates / plants / fungi / metazoa / bacteria), and the symbol-vs-ID stability problem.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ship workflow: prepare stages/commits locally; release pushes + opens a PR; publish handles issues + versioning. Use for 'ship', 'push', 'create a PR'. Official (→main) and beta (→dev) modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post-ship docs sync: cross-reference the diff and update README/ARCHITECTURE/CONTRIBUTING/AGENTS.md + CHANGELOG to match what shipped. Use on 'update/sync docs'; suggest after a PR opens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and implement infrastructure, container, CI/CD, deployment-safety, observability, and rollback changes. Does not read dotenv files or approve/release deployments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate initial docs/ from codebase analysis when a project has none. Triggers on 'init docs', 'create/generate documentation'. NOT for updating existing docs (mk:document-release).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ship workflow with explicit scopes: prepare stages and commits locally; release pushes and creates a PR; publish manages issues and versioning. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying. Supports official (→ main) and beta (→ dev/develop) ship modes with auto-detection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and review durable REST, GraphQL, RPC, or event API contracts: shape, compatibility, pagination, error semantics. Discovers existing consumers first. Not implementation, schema, or release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive JIRA workflow lifecycle via the jira-as wrapper: transition, assign, resolve, reopen, manage versions and components. Triggers: 'transition KEY to Status', 'mark KEY as Done', 'assign KEY to user', 'reopen KEY', 'release version', 'create component'. NOT for issue CRUD (mk:jira-issue); NOT for bulk transitions (mk:jira-bulk).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a project has no docs/ directory or needs initial documentation generated from codebase analysis. Triggers on "init docs", "create documentation", "generate docs", "docs init", or when docs/ is empty. Do NOT use for updating existing docs (use mk:document-release).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and implement infrastructure, containers, CI/CD, deployment safety, observability, and rollback changes. Use for Docker, IaC, cloud runtime, Kubernetes, pipeline, deployment, or operational reliability work. Does not read dotenv files or approve/release deployments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after code changes, before releases, or when testing features - runs the right level of QA based on what changed
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Invoke and resume YAML-defined pipelines by name — /pipeline auto-dev runs the full release pipeline
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full Self Driving — autonomous release loop that processes all auto-dev-eligible GitHub issues until none remain, by repeatedly running /pipeline auto-dev then /homework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-angle release quality verification using parallel expert review teams
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.