Refactor UAT skill: delegate to UAT_PLAYBOOK.md per plugin
- Rewrite skills/uat/SKILL.md to be a general UAT overview that delegates per-plugin test procedures to UAT_PLAYBOOK.md in each plugin repository (authoritative source of truth) - Add "What UAT Is NOT" section to explicitly prevent GitHub-browsing anti-pattern - Update SDLC skill to require UAT_PLAYBOOK.md as a required deliverable alongside code changes affecting plugin testing - Create UAT_PLAYBOOK.md in sealed-secrets and rook plugin repos Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
committed by
Gandalf the Greybeard [agent]
parent
c041da4847
commit
3abfe53a1e
@@ -69,6 +69,8 @@ Each promotion is a PR reviewed and merged by its gate owner:
|
||||
2. **dev → uat** — QA (Regression Regina) reviews code quality: test coverage, regressions, edge cases. QA merges to `uat` after approval.
|
||||
3. **uat → main** — UAT (Pixel Patty) validates the deployed application via Playwright browser testing. UAT merges to `main` after validation passes. For detailed UAT testing procedures, see the `uat` company skill.
|
||||
|
||||
**Playbook maintenance:** When plugin testing procedures change (new features, changed UI, different access paths), the engineer must update the plugin's `UAT_PLAYBOOK.md` in the same PR. This is a required deliverable alongside the code change — not optional cleanup.
|
||||
|
||||
**Each gate owner has merge authority.** No separate merge step by another role. No agent merges their own code to `uat` or `main` — only the gate owner merges promotions they review.
|
||||
|
||||
## Pipeline
|
||||
|
||||
Reference in New Issue
Block a user