suboss87/FDEOps / skills/review
review
VerifiedReview a proposed customer code change against its intended outcome and operational risks. Use for a diff or PR review; report evidence and actionable findings.
| File | Kind | Size |
|---|---|---|
| .fde-generated.json | config | 1.1 KB |
| SKILL.md | skill md | 1.3 KB |
| agents/openai.yaml | config | 212 B |
| references/build.md | markdown | 4.9 KB |
| references/debug.md | markdown | 3.6 KB |
| references/eval-pack.md | markdown | 6.2 KB |
| references/integrate.md | markdown | 4.7 KB |
| references/qa.md | markdown | 2.6 KB |
| references/review.md | markdown | 5.3 KB |
| references/ship.md | markdown | 10.6 KB |
| references/task-context.md | markdown | 6.6 KB |
| references/verification.md | markdown | 5.5 KB |
references/qa.md
View on GitHub# qa - Exercise the changed journey
Verify what the customer can do through the real interface, including the state the journey leaves behind.
**Use when:** a feature or fix needs behavioral verification, especially a UI, API, or multi-step workflow.
Follow [task context](task-context.md) and use existing browser, API, fixture, and test tooling. `.fde/` is optional. Every side effect must stay within the permitted environment and authority.
## Choose the journey and conditions
Identify the changed journey, user roles, acceptance checks, and neighboring paths at risk. Record revision and environment. Use synthetic or sanitized fixtures with understood cleanup; do not borrow production data without permission.
## Exercise the real interface
Run the normal journey from entry point to expected result. Verify persisted or downstream state when required; a success toast alone does not prove a write succeeded.
Choose negative and boundary cases relevant to the change: invalid input, empty/loading/error states, refresh/back navigation, retries, duplicates, permissions, or interruptions. For UI changes, use a real browser and inspect relevant viewport sizes, keyboard access, focus, labels, and errors.
Inspect relevant console and network evidence to distinguish UI defects from API failures or an unavailable environment. Keep only privacy-safe screenshots and logs. Code inspection or an unviewed generated screenshot does not establish visual verification.
## Resolve findings and repeat affected checks
Report defects with reproduction steps, expected and actual results, revision/environment, evidence, and impact. If repair is authorized, use [debug](debug.md), then rerun the failed journey and affected neighbors. Keep unrelated findings separate. Do not weaken acceptance to make a run pass.
*Fictional example:* Northstar's operator sees “Import complete,” but refreshing shows no new records. Check the downstream state and network response before reporting success or deciding whether the defect is in the page or the import service.
## Completion
Return a [verification receipt](verification.md) with checked journeys, observed results, reproducible defects, limitations, and blockers. Name roles, devices, environments, and data conditions that remain untested. Completion means agreed behavioral checks passed under the stated conditions.
A browser smoke test alone does not establish load capacity, security assurance, accessibility conformance, deployment, or customer acceptance. When coordinated, append evidence to the existing delivery record under its write rules; standalone QA can return the receipt directly.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |