메뉴
Use this skill when verifying a build, preparing a deployment, creating pull requests, running health checks, or managing a release. Load when the task is to get code from "merged" to "running in production" — or to confirm it is ready to be merged.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill when exploring a fuzzy idea, thinking through a concept from first principles, stress-testing assumptions, or crystallizing what you're actually trying to build before committing to a plan. Load when asked to brainstorm, when a problem statement is vague, or when the user is saying "I'm thinking about..." rather than "build this."
Use this skill when verifying that implementation work meets acceptance criteria, reviewing code for security vulnerabilities, assessing code quality and stability, or producing a formal review report. Load when conducting QA, security audits, or acceptance testing against a defined spec.
Use this skill when writing implementation plans, spec files, or step-by-step execution plans for engineers or sub-agents. Load when translating an architecture document and requirements into a concrete, ordered execution plan where each step must be self-contained and independently executable.
Use this skill when writing product requirements documents, defining acceptance criteria, or translating research and user needs into structured, testable specifications. Load when the task is to define what the system must do — not how — including functional requirements, non-functional requirements, user stories, acceptance criteria, and scope boundaries.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Manage the company knowledge vault at $HOME/workspace/context/ using Obsidian-compatible markdown and qmd search. Use when creating, searching, organizing, or linking company knowledge — memories, workflows, documents, decisions, or any persistent context.
| name | deploy-checklist |
| description | Use this skill when verifying a build, preparing a deployment, creating pull requests, running health checks, or managing a release. Load when the task is to get code from "merged" to "running in production" — or to confirm it is ready to be merged. |
| license | Proprietary. LICENSE.txt has complete terms |
Verify builds, manage deployments, create pull requests, run health checks, and handle release management. The status is binary: SHIPPED or BLOCKED. There is no "SHIPPED with warnings."
Before doing anything else, confirm:
Every check must pass. A single failure means BLOCKED.
any suppressions unless explicitly approved.Record the output of every check in the deployment report.
If the build toolchain is not provided, inspect package.json, Makefile, Cargo.toml, or equivalent to determine the correct commands.
Adapt to what exists:
CI/CD project:
Manual deployment:
No deployment needed:
# Deployment Report
## Branch
<branch> → <target>
## Build Status
| Check | Status | Details |
| ---------- | --------- | --------- |
| Lint | PASS/FAIL | <summary> |
| Type Check | PASS/FAIL | <summary> |
| Tests | PASS/FAIL | <summary> |
| Build | PASS/FAIL | <summary> |
## Deployment Status
<What was deployed, where, how. Or: "PR created — awaiting merge.">
## Health Verification
<Results. Or: "N/A — no deployment target.">
## Release Artifacts
- PR: <URL or N/A>
- Tag: <tag or N/A>
- Release Notes: <Updated / Created / N/A>
## Overall Status: SHIPPED | BLOCKED
### Blockers (if BLOCKED)
1. <What is broken and what must be done to fix it>