Quality

Completion Check verifies that infrastructure code is actually connected and invoked before marking work complete. Use it to trace execution paths, confirm hooks and database backends are registered, and run end-to-end tests.

Dead Code Detection finds unused functions and dead code in the codebase using TLDR static analysis. Use it to identify and remove dead code to keep the codebase clean.

Debug investigates logs, database state, and git history to help identify issues during manual testing or implementation without editing files. Use it to bootstrap a debugging session when something goes wrong and you need to gather evidence.

E2E Testing validates the entire persistence pipeline end-to-end. Use it when you need to verify that data flows correctly through the full stack.

Console Clear Logs clears the MCP log cache and the Unity Editor Console window, so subsequent log reads only show new entries. Use it before running a specific action to isolate errors or messages from that action.

Console Get Logs retrieves logs from the Unity Editor via the MCP plugin's LogCollector, optionally filtered by log type or time window. Use it to debug and monitor Editor activity.

PR Review Fix reviews unresolved comments on the GitHub pull request associated with the current branch, validates each comment, and fixes legitimate issues. Use it when you need to automatically triage and resolve PR review feedback.

Code Review Excellence teaches effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

Implementation Gap Validation analyzes gaps between approved requirements and an existing codebase to inform implementation strategy. Use it before design to identify missing capabilities, integration challenges, and viable implementation approaches.

Implementation Integration Validation checks completed feature tasks as a whole to catch cross-task integration issues, run the full test suite, verify spec coverage, and confirm design boundaries before a GO/NO-GO call. Use it after all tasks in a feature are implemented to decide whether the implementation is ready.

Kiro Debug investigates implementation failures using root-cause-first debugging, gathering evidence from errors, runtime config, and external docs to identify root cause and recommend the smallest safe next action. Use it when an implementer is blocked or verification fails.

Kiro Debug investigates implementation failures using root-cause-first debugging, gathering local evidence, runtime/config inspection, and external docs before proposing a fix. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.