kiro-debug

Root-cause debugging extracts exact error messages and stack traces, inspects repository state and dependency manifests, classifies the failure category, and produces a minimal fix plan with verification steps to resolve recurring test failures.

The best way to debug a blocked build is to collect structured evidence including failing commands and relevant git diffs, inspect runtime and repository state for missing prerequisites, and map the failure to a defined category for a targeted fix plan.

To triage verification failures, extract exact error text and stack traces, inspect dependency manifests and build configs for mismatches, and classify the cause into a standard category to produce a minimal repo-fixable plan with clear next actions.

Yes, this approach handles local repository failures by inspecting dependency manifests, build configs, and changed files to detect mismatches or missing prerequisites, combining local inspection with external documentation research when available.

To generate a concise debug report for verification failures, provide the exact failure message, relevant git diff, and a brief task description to produce ROOT_CAUSE, FIX_PLAN, VERIFICATION, and NEXT_ACTION outputs.

You should avoid minimal fix plans when implementation failures stem from systemic architectural mismatches rather than isolated errors, as this approach targets the smallest safe fix for blocked builds and recurring test or regression failures.