Menu
Use for product or UI QA, regression checks, generated artifact inspection, and release confidence reporting.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use only when the user explicitly allows bounded unattended execution of an approved Alloy task.
Use when encountering a bug, regression, failing command, or unexpected behavior before attempting a fix.
Use before planning when requirements are ambiguous, large, user-visible, or likely to cause rework unless decisions are locked.
Use when implementing an approved Alloy plan. Maintains progress.md, enforces TDD/debug discipline, and stops on blocked gates.
Use when a task needs broad source understanding before planning or execution.
Use when turning context or a clear user request into an implementation-ready plan with acceptance criteria, files, commands, gates, risks, and handoff.
| name | alloy-qa |
| description | Use for product or UI QA, regression checks, generated artifact inspection, and release confidence reporting. |
Use this skill when verification needs more than unit tests: UI flows, install output, generated files, docs/runtime parity, accessibility, or regression risk.
Write:
.alloy/tasks/<task-id>/qa.md
Also summarize important QA results in progress.md.
# <task-id>: QA
## Scope
- Included:
- Excluded:
## Environment
- Command/URL:
- Browser/device:
- Data/fixtures:
## Checks
| Area | Check | Result | Proof | Severity |
| --- | --- | --- | --- | --- |
## Regressions
- Before:
- After:
## Accessibility Or UX Notes
## Release Recommendation
- Ship / Ship with concerns / Block
verified only from QA impressions; tie it to commands or inspectable artifacts.progress.md.Report tier, checks run, failures, fixed issues, remaining risks, and release recommendation.