deployment-ops-edho-ferdian
Ship a build and keep it healthy: release strategy, CI/CD gates, health checks and Kubernetes, rollback, readiness verdict, dashboards, post-deploy watch, and production incidents with postmortems. Use for "deploy ini gimana", "pipeline CI/CD", "rollback", "siap rilis belum", "pantau setelah deploy", "production down", "ada insiden", "tulis postmortem".
- License 许可
- MIT
- 所属仓库
- edhoferdian/EEF
- 最近更新
- 2026-10-30
- Stars
- ★ 22
- Forks
- 0
01 前言 Front Matter
- name
- deployment-ops-edho-ferdian
- metadata
- { "last_reviewed": "2026-10-29" }
- description
- Ship a build and keep it healthy: release strategy, CI/CD gates, health checks and Kubernetes, rollback, readiness verdict, dashboards, post-deploy watch, and production incidents with postmortems. Use for "deploy ini gimana", "pipeline CI/CD", "rollback", "siap rilis belum", "pantau setelah deploy", "production down", "ada insiden", "tulis postmortem".
02 资源文件 7
- 参考文档references/cicd-pipeline.md11.0 KB
- 参考文档references/incident-response.md5.8 KB
- 参考文档references/kubernetes.md1.6 KB
- 参考文档references/observability.md2.3 KB
- 参考文档references/post-deploy-watch.md3.7 KB
- 参考文档references/production-readiness.md3.7 KB
- 参考文档references/release-strategies.md2.5 KB
03 SKILL.md 正文
Deployment Ops — Edho Ferdian Mode
Boundary — read before doing anything else
This skill owns the interval between "the image builds" and "the release is observably healthy". Everything on either side belongs elsewhere:
| Question | Skill that owns it |
|---|---|
| How do I structure the Dockerfile / compose file? | container-ops-edho-ferdian |
| Should this container run as root? Secrets in layers? | security-review-edho-ferdian |
| Is this page fast enough? What is the LCP budget? | performance-audit-edho-ferdian |
| Does this user journey still work? | e2e-testing-edho-ferdian |
| Is this deployed build broadly OK right now, once? | e2e-testing-edho-ferdian → qa-sweep.md |
| Should this be microservices? Which datastore? | system-design-edho-ferdian |
| Did I, the agent, actually finish the task I claimed? | safe-execution-edho-ferdian (delivery gate) |
That last row matters: safe-execution's delivery gate is about agent claim
discipline. references/production-readiness.md here is about application
risk. They ask different questions and must not restate each other.
Workflow
Step 1 Pick the release strategy → references/release-strategies.md Step 2 Wire the pipeline gates → references/cicd-pipeline.md Step 3 (K8s only) write the manifests → references/kubernetes.md Step 4 Production-readiness verdict → references/production-readiness.md (fans out to 4 risk-lens agents in parallel on a harness that supports delegation — see that file's "Delegation, not duplication" section) Step 5 Deploy, then watch → references/post-deploy-watch.md Step 6 Make it operable → references/observability.md Step 7 When production breaks → references/incident-response.md (mitigate before diagnosing; read-only until a mitigation is approved; postmortem)
references/cicd-pipeline.md (Step 2) covers gate ordering (lint → typecheck
→ unit test → security scan → build → deploy) with rationale, GitHub
branch-protection required-status-checks setup, a full concrete GitHub
Actions workflow with parallel gates and a branch/event-guarded deploy job,
lockfile-hash-keyed caching, and the fail-fast-vs-fail-informatively
distinction.
Language routing (fixed — see skill-authoring-edho-ferdian's canonical contract)
Communication to the user in Bahasa Indonesia; deploy/rollback commands,
config, and status output in English — fixed, never ask. Full contract:
skill-authoring-edho-ferdian §7.
Global rules
- Never claim a deploy is healthy from the deploy tool's exit code. The pipeline says "deployed"; only Step 5 says "healthy".
- A release without a written rollback path is not ready — this is a hard cap in Step 4, not a suggestion.
- Deploying to production is a destructive-class action: run
safe-execution-edho-ferdianGate 2 before executing one.
04 同仓库更多 Skills
video-style-edho-ferdian
Measure a reference video's look and pacing (colour grade as a 3D LUT, cut rhythm, overlays) and reproduce it: grade, cut and composite new footage, verify numerically, hand off an NLE timeline. Use for "tiru look video ini", "samakan grading", "bikin video dengan gaya referensi", "LUT dari referensi", "cut rhythm".
test-authoring-edho-ferdian
Write unit and component tests well: React Testing Library, pytest, Go and Vue, plus regression-test patterns. Use for "tulis test untuk component ini", "bagaimana test hook ini", "test yang bagus untuk fitur X", "tulis test pytest/Go/Vue", or dev-kickoff's TEST stage.
system-design-edho-ferdian
Mid-project architecture decisions: ADRs, trade-off analysis, non-functional requirements, scaling tiers and blast radius. Use for "desain arsitektur", "keputusan teknis besar", "bikin ADR", "trade-off antara X dan Y", "microservices atau monolith", "apa yang rusak kalau X diubah", or a capacity question.
spec-mining-edho-ferdian
Extract behavioural specs from a codebase with none: WHEN/THEN requirements and invariants, each anchored to the code that enforces it, unclear behaviour recorded as uncertainty. Use for "ekstrak spec", "buat spec dari kode", "reverse-engineer the spec", "repo ini tidak ada dokumentasi", or a missing BEHAVIOR_SPEC in dev-kickoff.
skill-authoring-edho-ferdian
Create and govern this ecosystem's skills: search before building, a quality bar, compliance checks, promoting repeated principles to rules, and packaging dist/*.skill. Use for "bikin skill baru", "ada skill buat X gak", "fork skill ini", "skill gue kepake gak sih", "package skill ini", "buatkan .skill-nya".
skill-audit-edho-ferdian
Audit this repo's skills/ for staleness, redundancy, broken cross-references and weak descriptions (not the ~/.claude setup: that is config-hygiene). Use for "audit skill saya", "cek skill yang sudah dibuat", "ada yang redundan gak", "skill mana yang basi".