@edupia-tutor/spec-driven-docs 0.14.0 → 0.14.2

package/commands/qc-review.tmpl

@@ -4,14 +4,14 @@ updated: 2026-06-11
 ported_from: ai-automation-qc-base
 ---
 
-# /qc-review — QC Review Gate (test cases & scripts)
+# /qc-review — QC Review Gate (test case & script)
 
-> Stage 4 of the native QC automation pipeline (qc-analyze → qc-plan → qc-design-test → qc-review → qc-run-test → qc-report). Ported from the QC team's qa-reviewer. A two-way gate: reviews test cases (after qc-design-test) AND scripts (after qc-run-test).
+> Stage 4 của QC automation pipeline native (qc-analyze → qc-plan → qc-design-test → qc-review → qc-run-test → qc-report). Port từ qa-reviewer của team QC. Một gate hai chiều: review test case (sau qc-design-test) VÀ script (sau qc-run-test).
 
 ## Gate
 {{include:steps/gate.md}}
 
-*Note: For this command, the target in Step 1 is a UC-ID. Detect review mode from `$ARGUMENTS`/context: review test-case `.Test.md` (after design) or review Python scripts (after run). Read artifacts from `{paths.qc_dir}/{UC-ID}/` and the generated test/page-object source.*
+*Lưu ý: Với lệnh này, target ở Bước 1 là một UC-ID. Phát hiện review mode từ `$ARGUMENTS`/context: review test-case `.Test.md` (sau design) hoặc review Python script (sau run). Đọc artifact từ `{paths.qc_dir}/{UC-ID}/` và source test/page-object đã sinh.*
 
 ## Context
 {{include:steps/context-loader.md}}
@@ -20,34 +20,34 @@ ported_from: ai-automation-qc-base
 
 ## Role
 
-You are the **QC Reviewer** — the shared review gate, run twice in the pipeline:
-1. **After qc-design-test** → review the test-case `.Test.md` (coverage, clarity, trace).
-2. **After qc-run-test** → review the generated Python scripts / Page Objects.
+Bạn là **QC Reviewer** — gate review dùng chung, chạy hai lần trong pipeline:
+1. **Sau qc-design-test** → review test-case `.Test.md` (coverage, độ rõ ràng, trace).
+2. **Sau qc-run-test** → review Python script / Page Object đã sinh.
 
-Detect mode: if the target artifacts are `.Test.md` → test-case review; if Python test/PO
-files exist for the UC and are newer → script review. If ambiguous, ask.
+Phát hiện mode: nếu artifact target là `.Test.md` → review test-case; nếu file Python test/PO
+tồn tại cho UC và mới hơn → review script. Nếu mơ hồ, hỏi.
 
 ## Skills (`{paths.qc_skills_dir}/qa-reviewer/`)
 
-Pick by mode + layer, load ONE file:
-- Test-case review: `test-case/{functional,e2e,integration,non-functional,exploratory}.md`
-- Script review: `script/{functional,e2e,integration,non-functional,exploratory}.md`
+Chọn theo mode + layer, nạp MỘT file:
+- Review test-case: `test-case/{functional,e2e,integration,non-functional,exploratory}.md`
+- Review script: `script/{functional,e2e,integration,non-functional,exploratory}.md`
 
 ## Review focus
 
-- **Test-case:** every `{UC-ID}-SC{N}` covered? happy + negative + boundary? concrete expected? trace (`BR-xx` + `@trace.verifies` SC) present? no orphan TC?
-- **Script:** matches the `.Test.md` 1-1? Page Object 3-layer + slim BasePage? `expect()` not bare assert? no hard-coded URL/cred/timeout, no `time.sleep`, no Allure? selectors per priority (data-testid→role→…)? 100% of TCs scripted (none left Draft)?
+- **Test-case:** mọi `{UC-ID}-SC{N}` đã phủ? happy + negative + boundary? expected cụ thể? trace (`BR-xx` + `@trace.verifies` SC) có mặt? không có TC orphan?
+- **Script:** khớp `.Test.md` 1-1? Page Object 3 lớp + BasePage gọn? `expect()` không phải bare assert? không hard-code URL/cred/timeout, không `time.sleep`, không Allure? selector theo priority (data-testid→role→…)? 100% TC đã script (không còn Draft)?
 
-Produce findings (severity + location + fix). Verdict APPROVED or NEEDS_FIX.
+Sinh findings (severity + vị trí + fix). Verdict APPROVED hoặc NEEDS_FIX.
 
 ## Report
 
 {{include:steps/report-footer.md}}
 
 ```
-/qc-review Complete — {UC-ID} ({test-case | script} review)
+/qc-review Hoàn tất — {UC-ID} ({test-case | script} review)
 Verdict: {APPROVED | NEEDS_FIX} — {N} findings ({crit} critical)
 Next (test-case APPROVED): /qc-run-test {UC-ID}
-Next (script APPROVED)   : /qc-report {UC-ID}  then create PR
-     (NEEDS_FIX → fix the flagged artifact, then re-run /qc-review {UC-ID})
+Next (script APPROVED)   : /qc-report {UC-ID}  rồi tạo PR
+     (NEEDS_FIX → fix artifact bị gắn cờ, rồi chạy lại /qc-review {UC-ID})
 ```