Skip to content

arjun988/blender-skills / .claude/skills/qa-review

qa-review

Verified

Production QA gate for Blender assets using viewport screenshots, validation checklists, naming audits, and ship/no-ship verdicts via MCP.

QA Review

Screenshot-backed review. Checklist gate. Explicit ship / no-ship.

When to Use

  • Before export or handoff
  • After major modeling/lookdev milestones
  • Reference-match final compare
  • Periodic scene health checks

Workflow

Gather brief budgets → Screenshot key angles → Run checklists
  → List defects (severity) → Fix or reject → Re-verify → Verdict

Required Screenshots

  1. 3/4 hero angle
  2. Ortho or profile if proportion-critical
  3. Wireframe or poly overview (optional but useful)
  4. Material/light beauty
  5. Vs reference (if reference task)

Use get_viewport_screenshot via MCP when connected.

Checklists (load as needed)

  • ../references/validation-checklist.md
  • ../references/visual-match-checklist.md (reference tasks)
  • ../references/naming-conventions.md
  • ../references/polycount-budgets.md

Defect Severity

LevelMeaning
BlockerWrong scale, broken normals, fails budget badly
MajorSilhouette/readability issues, bad pivots
MinorNaming, minor shading, small gaps
NoteOptional polish

Verdict Template

## QA Verdict: [Asset]

**Result:** SHIP / SHIP WITH NOTES / NO-SHIP
**Budgets:** [tris/textures] vs target
**Screenshots:** [listed]
**Blockers:** ...
**Majors:** ...
**Minors:** ...
**Next actions:** ...

Constraints

MUST DO

  • Give explicit verdict
  • Attach or capture screenshots for visual claims
  • Re-check after fixes before flipping to SHIP

MUST NOT DO

  • Rubber-stamp without screenshots on visual tasks
  • Ignore budget overruns without approval

Reference Guide

TopicReferenceLoad When
Qa Verdict Templatereferences/qa-verdict-template.mdWhen needed
Screenshot Anglesreferences/screenshot-angles.mdWhen needed
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall