菜单
Docker and Docker Compose containerization. Trigger when the user wants to dockerize an application or create containers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
Perform a thorough code review. Use when the user requests a review, wants to verify code quality, or before merging a PR.
Context transfer between AI sessions. Trigger when the user wants to save the context, resume a task, or hand off the work to another session.
API mock configuration for tests. Trigger when the user wants to mock APIs, use MSW, or test without a backend.
Debug and resolve problems. Use when the user has a bug, an error, an unexpected behavior, or wants to understand why something is not working.
TDD development with Red-Green-Refactor cycle. Use to implement a feature by writing tests BEFORE the code. Trigger automatically when the user asks for TDD, wants to write tests first, mentions "test first", or asks to implement, add, create, fix, correct code, a new feature, a bugfix, or a functionality.
| name | ops-docker |
| description | Docker and Docker Compose containerization. Trigger when the user wants to dockerize an application or create containers. |
| allowed-tools | ["Read","Write","Edit","Bash","Glob","Grep"] |
| context | fork |
| disable-model-invocation | true |
Dockerfile syntax, Compose schema and image-publish flows drift on each release and are canonical at:
RUN addgroup -S app && adduser -S app -G app && USER app — never run app code as root inside the container, even if "it's just a sandbox"..git/ or node_modules/ in the build context bloats images by hundreds of MB and leaks secrets. The .dockerignore rules mirror your .gitignore plus build artifacts.node:20-alpine, not node:latest or bare node:20): floating tags break reproducibility; SHA pinning is overkill for most apps but worth it for security-critical builds.COPY .env or hardcode credentials in ENV. Use BuildKit secrets (--mount=type=secret) or runtime-injected env vars from the orchestrator./ops:ops-deploy — deployment checklist consumes the built image/ops:ops-database — Compose patterns for DB services (depends_on: { condition: service_healthy })qa-security — image scanning gate (Snyk/Trivy) before pushops-ci — Hadolint + image scan as CI steps