| name | review-changes |
| description | Reviews existing Pixel Creator changes for correctness, architectural regressions, contract violations, unnecessary complexity, test coverage, and unintended side effects. Use when reviewing a diff, recent implementation, branch, or proposed change. |
Review Pixel Creator Changes
Procedure
- Inspect the complete diff.
- Identify the intended behavior.
- Trace affected code paths.
- Inspect relevant tests.
- Inspect relevant documentation and ADRs.
- Check architectural boundaries.
- Check API and identity contracts.
- Check error handling and state mutation.
- Check for unnecessary complexity or unrelated changes.
- Run relevant tests when possible.
Review priorities
Prioritize:
- Incorrect behavior.
- Architectural contract violations.
- Regressions.
- Incorrect state ownership.
- Missing or misleading tests.
- Unnecessary complexity.
- Maintainability concerns.
- Style issues.
Do not report stylistic preferences as critical issues.
Pixel Creator-specific checks
Verify especially:
- Core remains platform-independent;
- Runtime remains headless-capable;
- Scene/Object/ResourceId identities are not conflated;
- Pixel Creator
Object is not confused with native JavaScript Object;
- Property System reactivity is preserved;
- transform composition remains correct;
- Runtime errors do not automatically mutate component state;
- ADR-0012 remains respected;
- editor-specific concerns do not leak into Core;
- no unnecessary dependency or framework has been introduced.
Output
Group findings by severity:
Critical
Must be fixed.
Important
Should be fixed before merging.
Minor
Useful improvement but not blocking.
Positive
Notable decisions that are correct or particularly clean.
Do not modify files unless explicitly requested.
