Menu
Use to verify if the code/logic aligns with the Vietnamese business spec. Mandatory cross-referencing with BR-* rules before implementation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
Use to review Go backend changes for correctness, security, modular-monolith boundaries, error handling, SQL safety, domain invariants, and missing tests. Trigger when the user asks for code review, PR review, audit findings, or correctness/security review.
| name | business-auditor |
| description | Use to verify if the code/logic aligns with the Vietnamese business spec. Mandatory cross-referencing with BR-* rules before implementation. |
Ensures every line of Backend code complies with docs/backend-business-logic-vi.md.
docs/backend-business-logic-vi.md file is the ultimate authority. Code must adapt to the spec, not vice versa.service.go must be tagged or justified by a specific rule (e.g., BR-K03, BR-P01).Before modifying code, list the relevant business rules:
Check if the code violates these critical invariants:
used_area + remnant_area <= source_area.COMPLETED status.ValidateTransition functions.AVAILABLE remnants don't accidentally become CONSUMED without a valid RecordCut event.BizError reflecting the specific rule violation?Note: If you find missing or contradictory logic in the spec, stop and ask the User (Indie Hacker) to update the documentation first.