qa-validation

Verify Unity DOTS changes with static and runtime checks.

6|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/dyCuong03/unity-agent-team --skill qa-validation-dycuong03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-validation
Source: https://github.com/dyCuong03/unity-agent-team/tree/main/.claude/skills/qa-validation
Command: npx skills add https://github.com/dyCuong03/unity-agent-team --skill qa-validation-dycuong03

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you validate Unity DOTS changes with rigorous, evidence-backed correctness checks instead of intuition or incomplete markdown “promises.”

Core Features & Use Cases

  • Static + Runtime Verification Contract: requires both compile/architecture safety checks and executable runtime proof before a change is considered verified.
  • DOTS-focused ECS verification guidance: validates baker output, component state transitions, system ordering, entity lifecycle, determinism, and Burst safety patterns.
  • Stress and regression coverage: defines stress targets (frame time, memory, determinism, race risk) and enforces regression evidence with reproduction-ready reporting.
  • Tester/Verifier output requirements: standardizes what must be written into workspace/verification_result.json, including blocking issues and confidence/risk levels.

Quick Start

Use the qa-validation skill to produce a verification plan and report that satisfies the Tester Runtime + Static Verification Contract for your Unity DOTS change.

Frequently Asked Questions about qa-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Unity DOTS changes with runtime proof instead of manual testing?

Verify Unity DOTS changes by generating compile-safe static checks alongside executable runtime evidence in EditMode and PlayMode. This approach enforces a static plus runtime verification contract, producing a structured JSON report with blocking issues and confidence levels.

What is the best way to test baker output and system ordering in Unity ECS?

Testing baker output and system ordering in Unity ECS requires designing executable runtime proofs that validate component state transitions and entity lifecycle. This ensures deterministic behavior and validates Burst safety patterns across refactors.

How do I perform stress testing for Unity DOTS to check frame time and determinism?

Perform Unity DOTS stress testing by defining specific targets for frame time, memory usage, and determinism. This process generates regression evidence with reproduction-ready reporting to evaluate race risk and release-readiness.

Does Unity DOTS verification require both static and runtime checks for a feature fix?

Yes, Unity DOTS verification requires both static architecture safety checks and executable runtime proof before considering a feature fix verified. This dual-layer conformity ensures changes are evidence-backed rather than relying on incomplete manual checks.

What format should Unity DOTS verification results be written to for regression coverage?

Unity DOTS verification results must be written to workspace/verification_result.json. This standardized output file captures both static and runtime evidence layers, including blocking issues and assigned confidence or risk levels.