메뉴
Use when asked to deploy, prepare a release, run pre-deploy checks, or before shipping code to production; ensures typecheck, lint, tests, build, migrations, env vars, and breaking changes are reviewed before release.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user wants the Claude `/deploy` command workflow in Codex, or asks to run `deploy` using the claudet command template.
Use when the user wants the Claude `/fix-issue` command workflow in Codex, or asks to run `fix-issue` using the claudet command template.
Use when the user wants the Claude `/review` command workflow in Codex, or asks to run `review` using the claudet command template.
Use when syncing, auditing, or converting Claude Code and Codex project configuration; when the user says "sync agent configs", "convert Claude project to Codex", "convert Codex project to Claude", "make this project work with both Claude and Codex", or asks to keep AGENTS.md, CLAUDE.md, .claude, .codex, .mcp.json, agents, commands, and skills aligned.
Use when starting a new project from scratch and wanting Claude Code or Codex conventions; when the user says "scaffold from the template", "use claudet", "set up a new project", "init claude config in this repo", "init codex config in this repo", or asks to copy rules/agents/commands/claudedocs structure from the claudet template repo.
Use when the user wants to install or update the claudet rule library (`code-style`, `naming-and-comments`, `file-and-module-structure`, `dependency-management`, `testing`, `api-conventions`, `documentation`) into the current project's `.claude/rules/`; when the user says "sync rules from claudet", "install standard rules here", "update rules in this project", or asks why their rules look outdated compared to claudet's.
| name | deploy |
| description | Use when asked to deploy, prepare a release, run pre-deploy checks, or before shipping code to production; ensures typecheck, lint, tests, build, migrations, env vars, and breaking changes are reviewed before release. |
Execute a structured, safe deployment checklist to ensure nothing is missed before shipping to production.
npm run typecheck # Zero TypeScript errors required
npm run lint # Zero lint errors required
npm run test # All tests must pass
npm run build # Build must succeed
Stop and report if any phase fails. Do not proceed to Phase 2.
npx prisma migrate status
prisma migrate deploy without explicit developer confirmationdb-migration-safety skill to review the SQL for DROP, RENAME, NOT NULL, foreign keys, or large indexes against populated tables — these need expand-contract, not a single-step deploy.env.example against the last deploy tag to find newly added varsDraft a release summary:
## What Changed
[bullet list of features/fixes]
## How to Test
[steps to verify key flows in production]
## Database Changes
[list of migrations, or "None"]
## New Environment Variables
[list, or "None"]
## Rollback Plan
[steps to revert if needed]
## Risk Level
[ ] Low — bug fix, no schema change
[ ] Medium — new feature, additive changes only
[ ] High — breaking change, schema migration