agf-writing-qa-reportlisted

# Writing a QA Report (E2E / UAT) Use this skill when: - E2E execution is complete and a report needs publishing - UAT business sign-off needs to be captured - A bug-fix E2E re-verification needs recording (always **appended** as `## Re-run [N] — [date]` to the existing `[feature]-e2e-[YYYY-MM-DD].md`; never a new file — see "File path & naming" below) **Pair with**: - `agf-running-sit-tests` skill — SIT 由 dev 自跑，本 skill 不覆盖 SIT 报告（SIT 证据已在 `progress/<role>.md` 的 `**SIT 证据**` 段，归档随 `docs/qa/<feature>-process-log.md` 走） - This skill — covers the **E2E / UAT artifact** (report file) format ## File path & naming `docs/qa/[feature-kebab-case]-[stage]-[YYYY-MM-DD].md` — Stage ∈ `{e2e, uat}`. Examples: - `docs/qa/oauth-login-e2e-2026-05-13.md` - `docs/qa/oauth-login-uat-2026-05-15.md` **One report per stage per feature.** Re-runs after defect fix → append a new `## Re-run [N] — [date]` section to the same file, do not create a new file. ## Required sections (in order) ```markdown # QA Report — [Feature] — [E2E|UAT] - **Date**: YYYY-MM-DD - **Stage**: E2E / UAT - **Tester**: qa-engineer ([model name]) / 业务方姓名（UAT） - **Branch**: [branch + commit hash] - **Environment**: local docker-compose / staging / pre-prod - **PRD**: docs/prd/[feature]-[date].md - **Code review (含 SIT Audit)**: docs/reviews/[feature]-[date].md ## Summary - Total AC: N - Passed: M - Failed: K - Blocked: J - **Verdict**: ✅ Promote to next stage / ❌ Block / ⚠️ Conditional promote ## Pre-conditions Check