@edupia-tutor/spec-driven-docs 0.14.0

package/skills/code/SKILL.tmpl

@@ -0,0 +1,176 @@
+---
+description: Generates implementation code from approved BDD specs with traceability tags, or performs a read-only code review against spec compliance and architecture rules. Trigger when: "/generate-code", "/review-code", "sinh code", "generate code", "viết code", "implement feature", "review code", "kiểm tra code", "code review", "check implementation".
+---
+
+# Code Skills — Generate & Review
+
+This skill handles `/generate-code` (implementation) and `/review-code` (read-only review).
+
+---
+
+## /generate-code — Generate Implementation Code
+
+### Gate
+
+<!-- Directory: specs/*/*/bdd/*.feature -->
+{{include:steps/gate.md}}
+
+4. Check for existing trace state: read `.trace/{domain}/{prd-slug}/{UC-ID}.tsv` if it exists.
+   - Identify: new scenarios vs. drifted (changed) vs. synced (skip)
+
+5. Show **CHECKPOINT — Comprehension**:
+   ```
+   I understand:
+   - Feature: {name} | Ticket: {TICKET_ID if known}
+   - UC: {UC-ID} in domain: {domain}
+   - Scenarios: {N} total ({X} new, {Y} drifted, {Z} synced-skip)
+   - Layer order: {from CLAUDE.md architecture}
+   - Files to create/update: [list in generation order]
+
+   Proceed? (Y/N)
+   ```
+   Wait for confirmation.
+
+### Context Load
+
+{{include:steps/context-loader.md}}
+
+Also read:
+- `.feature` file (what to implement)
+- Tech doc `specs/{domain}/{prd-slug}/tech-docs/{UC-ID}-tech-design.md` (if exists)
+- Existing entity/model files in this domain (to follow patterns)
+
+### Branch
+
+Create a feature branch:
+```bash
+git checkout -b feature/{TICKET_ID}-{slug}
+# If no ticket ID: feature/{UC-ID}-{slug}
+```
+
+### Generate
+
+Generate code in layer order (adapt to your stack):
+
+**For a typical layered backend (e.g., Controller → Service → Repository):**
+
+1. **DTOs / Request-Response models** — input validation, output shape
+2. **Domain entity / model** — data representation
+3. **Repository / Data Access** — queries, filters
+4. **Service interface** — contract
+5. **Service implementation** — business logic, `@Transactional` where needed
+6. **Facade interface** (if architecture uses facade layer) — orchestration contract
+7. **Facade implementation** — cross-service orchestration
+8. **Controller / Handler** — HTTP mapping, auth, `@trace` tags
+
+**Critical: Traceability tags on every controller method:**
+```
+# @trace.implements={UC-ID}-SC{N}
+# @trace.source=specs/{domain}/{prd-slug}/bdd/{UC-ID}.feature
+```
+(Use your language's comment syntax)
+
+### Self-Review (3 rounds)
+
+After generating, verify:
+- [ ] Every scenario in .feature has a corresponding controller endpoint
+- [ ] `@trace.implements` tag on every endpoint
+- [ ] Architecture layer rules respected (from CLAUDE.md)
+- [ ] Error handling matches CLAUDE.md §error_handling
+- [ ] No magic numbers, no debug logging
+- [ ] Coding standards from CLAUDE.md followed
+
+If issues found → fix inline before proceeding.
+
+### Build Verify
+
+```bash
+{BUILD_COMMAND}   # from project-context.yaml, max 3 retries
+```
+
+If build fails: read error, fix, retry. After 3 failures, report to user with diagnosis.
+
+### Write Trace State
+
+Update `.trace/{domain}/{prd-slug}/{UC-ID}.tsv`:
+```
+UC-ID\tSC-ID\tsc_version\timplemented_by\tlast_updated
+{UC-ID}\tSC1\t{hash of scenario text}\t{ControllerClass}.{method}\t{date}
+```
+
+### Commit
+
+```bash
+git add {changed files}
+git commit -m "{commit_format from CLAUDE.md}: {description}"
+```
+
+### Report
+
+```
+/generate-code Complete — {UC-ID}
+- Files created: {N}  |  Updated: {M}
+- Build: SUCCESS (attempt {K}/3)
+- Branch: feature/{TICKET_ID}-{slug}
+- Trace: .trace/{domain}/{prd-slug}/{UC-ID}.tsv updated
+```
+
+{{include:steps/report-footer.md}}
+
+---
+
+## /review-code — Read-Only Code Review
+
+**IMPORTANT**: This is READ-ONLY. Report issues but do NOT make changes.
+
+### Input
+
+Accept: UC-ID, file path, or current branch name.
+
+### Review Dimensions
+
+#### 1. Traceability
+- [ ] Every controller endpoint has `@trace.implements` tag?
+- [ ] Every test file has `@trace.verifies` tag?
+- [ ] No `@trace` tags on non-controller layers (Service, Repository, etc.)?
+- [ ] `.trace/{domain}/{prd-slug}/{UC-ID}.tsv` is up to date?
+
+#### 2. Layer Architecture (from CLAUDE.md)
+- [ ] Each class is in the correct layer?
+- [ ] Layer dependencies flow in the right direction?
+- [ ] No layer is bypassed (e.g., Controller calling Repository directly)?
+
+#### 3. Coding Standards (from CLAUDE.md)
+- [ ] Naming conventions followed?
+- [ ] Response wrapper used consistently?
+- [ ] Exceptions thrown (not swallowed or manually built into responses)?
+- [ ] No magic numbers?
+- [ ] No sensitive data in logs?
+- [ ] Transaction annotations correct?
+
+#### 4. Spec Compliance
+- [ ] Every scenario in .feature has an implementation?
+- [ ] No undocumented endpoints (code not backed by spec)?
+
+### Output
+
+```
+/review-code Report — {UC-ID}
+Critical: {X}  |  Major: {Y}  |  Minor: {Z}
+
+### Critical
+| # | File | Line | Issue | Suggested Fix |
+|---|------|------|-------|---------------|
+
+### Major
+| # | File | Line | Issue | Suggested Fix |
+
+### Minor
+| # | File | Line | Issue | Suggested Fix |
+
+Verdict: APPROVED ✅ | NEEDS_FIX ❌
+```
+
+If `NEEDS_FIX`: list specific files to change and run `/fix-bug` or correct inline.
+
+{{include:steps/report-footer.md}}