Quality

GdUnit4 Test Driver runs Godot gdUnit4 unit tests and parses the results into structured output. Use it after code changes, when test failures need diagnosis, or when writing new GDScript or C# tests.

Godot Maker Evaluate checks the current tag’s game quality against the playable-unit gate and keeps the flat e2e suite aligned with supported mechanics. Use it after verify to add, restore, or prune gameplay tests for the current tag.

Godot Verify runs mechanical checks on a built Godot project, including headless build, unit tests, lint, and static checks. Use it after /gm-build or /gm-fixgap to confirm the game is ready for evaluation.

Canonical Review orchestrates multi-agent code review with specialist perspectives and structured findings. Use it to review a PR, branch, staged changes, or files and synthesize actionable issues.

Debug systematically diagnoses and resolves bugs through conversational investigation, reproduction, and root cause analysis. Use it when you need to trace a failure, test hypotheses, and verify a minimal fix.

Pattern Detection identifies naming, architecture, testing, and organization patterns in an existing codebase so new code can match established conventions. Use it when generating code, reviewing changes, or checking for conflicts.

Refactor improves code structure, naming, and readability while preserving existing behavior. Use it when you need to simplify implementation details without changing business logic or public contracts.

Review coordinates multi-agent code review across security, performance, patterns, simplification, and tests. Use it to gather synthesized feedback on code changes with strengths and actionable findings.

Test runs the full test suite, including unit, integration, and E2E categories, to verify changes and enforce code ownership. Use it when implementation changes, bugs, or refactors need proof that everything still passes.

Validate orchestrates spec, file, drift, comparison, and constitution checks across artifacts. Use it when reviewing a spec, checking a file, detecting implementation drift, or comparing two sources.

Verification Before Completion requires building, testing, and linting a change before you say it is finished. Use it when you need to confirm a coding task works and has no obvious regressions.

Artifact Contract Auditor checks whether completed Units and the locked Pipeline have all required output files present, then writes output/CONTRACT_REPORT.md. Use it for mid-run coverage snapshots or final delivery completeness, not provenance checks.