菜单
Use to prepare a backend release, validate release readiness, check migrations and documentation, plan version bumps, and summarize release steps. Trigger when the user asks for release prep, tagging, versioning, go-live checklist, or release notes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use to verify if the code/logic aligns with the Vietnamese business spec. Mandatory cross-referencing with BR-* rules before implementation.
Use when the user asks to deploy, dockerize, set up CI/CD, configure environments, or prepare for go-live. Covers Docker Compose, GitHub Actions, health checks, environment configuration, database backup, and production readiness checklist. Trigger words: "deploy", "docker", "CI", "CD", "go live", "production", "staging", "health check", "backup", "monitoring".
Use to ensure alignment between Backend and Frontend, guarding the Modular Monolith and API contracts.
Use to analyze the backlog, break down tasks from requirements, and automate Issue/Sprint management using GitLab API.
Use to audit and enforce role-based access control (RBAC) across all API endpoints. Scans handler routes, maps required roles from the business spec, generates RequireRole middleware guards, and reports orphan (unprotected) endpoints. Trigger words: "rbac", "phân quyền", "role", "access control", "security audit", "guard endpoints", "protect routes".
Use when starting ANY non-trivial issue or feature on the Go backend — covers the full Senior Engineer workflow: requirements clarification -> technical design -> task breakdown -> implement + test -> self-QA -> PR. ALWAYS trigger this skill when the user says "implement", "add feature", "fix issue", "build", "create endpoint", or pastes a GitHub issue/ticket. Do NOT skip phases — especially Phase 5 (Self-QA) which is the most commonly forgotten step before submitting code.
| name | release |
| description | Use to prepare a backend release, validate release readiness, check migrations and documentation, plan version bumps, and summarize release steps. Trigger when the user asks for release prep, tagging, versioning, go-live checklist, or release notes. |
You are preparing a release for the VMARBLE Warehouse Management Service.
make test passes (all tests green, no race conditions)make lint passes (no linter warnings)make build succeeds (binary compiles cleanly)Up and Down functionsmake migrate-up runs cleanly on a fresh databasemake migrate-down can rollback without data lossREADME.md is up to dateCLAUDE.md reflects any new conventions or modulesmake swaggerdev via PRdev → main PR created with at least 1 approvaldev branch is stable and all PRs mergeddev → mainRelease vX.Y.Z — brief descriptionmaingit tag vX.Y.ZFollow semantic versioning: