ワンクリックで
docker-deployment
When the user mentions "docker deployment", "docker", "deployment". When the user needs help with docker deployment.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
When the user mentions "docker deployment", "docker", "deployment". When the user needs help with docker deployment.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | docker-deployment |
| description | When the user mentions "docker deployment", "docker", "deployment". When the user needs help with docker deployment. |
| allowed-tools | ["Bash","Read","Write","Edit","Glob","Grep"] |
| triggers | ["docker deployment","docker","deployment"] |
| metadata | {"tags":["docker","deployment"]} |
[One sentence: what problem does this solve and for whom.]
Activate when user requests:
Do NOT activate for: [list false-positive phrases]
# command
[description]
Verify the output is correct and tests still pass.
[What artifact or state results from applying this skill.]
❌ [What NOT to do] ✅ [What to do instead]
When the user wants to add a new feature or capability. When the user says "I want to build" or "I'm thinking about". When requirements are unclear and need to be refined.
When the user says they are ready for review or wants to create a PR. When the user asks to check if code is ready for review. When the task or feature is complete and needs quality validation.
When the user approves a plan and wants to execute it. When the user says "execute the plan" or "let's go" or "start implementation". When a PLAN.md exists and is ready to be executed task-by-task.
When the user is implementing a new feature or fixing a bug. When the user wants to write tests first before writing code. When the user is refactoring and needs to verify behaviour is preserved.
When the user wants to create an implementation plan. When the user says "let's implement this" or "create a plan". When a design has been approved and is ready to be broken into tasks.
Systematic code review workflow — evaluate changes for correctness, style, security, and test coverage before merging. When the user asks to review code or a pull request. When the user says "check code quality" or "look over this diff". When the user requests feedback on changes before merging.