kiro-debug

Investigate implementation failures and produce a root-cause analysis with a fix plan.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-debug-taku-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-debug
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-debug
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-debug-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This skill helps implementers and reviewers rapidly identify the true root cause of implementation failures by gathering evidence, inspecting runtime and repository state, and classifying the underlying issue so that the smallest safe remediation can be applied.

## Core Features & Use Cases

  • Evidence-first analysis: extract exact error text, stack traces, failing commands, and relevant git diffs to avoid speculative fixes.
  • Runtime and configuration inspection: examine dependency versions, build/runtime configs, and changed files to detect mismatches and configuration gaps.
  • Structured remediation & escalation: classify causes into predefined categories and produce a minimal, verifiable fix plan or an explicit escalation when human decisions are required; typical when builds fail, verification regresses, or reviewer rejections repeat.

### Quick Start Run kiro-debug with a concise failure summary, the error output and stack trace, the relevant git diff, and any applicable spec or implementation notes to receive a structured debug report including root cause, fix plan, verification, and next action.

Frequently Asked Questions about kiro-debug

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

FAQPage Schema
How do I find the root cause of a failing build using git diffs and stack traces?

Runtime debugging inspects dependency versions, build configurations, and changed files to detect mismatches. It combines local repository inspection with configuration checks to identify the underlying cause of verification regressions.

What's the best way to debug a reviewer rejection when my implementation task is blocked?

Evidence-first failure analysis extracts exact error text and relevant git diffs to avoid speculative fixes. It classifies reviewer rejections into predefined categories and produces a minimal repo-fix plan or explicit escalation for blocked implementation tasks.

Can I use automated triage for runtime configuration gaps that cause implementation failures?

Yes, runtime and configuration inspection examines dependency versions and build configs to detect gaps. Automated triage combines local repository inspection with curated web research to classify causes and generate verification steps.

Do I need to provide error output and implementation notes for failure analysis to work?

You need a concise failure summary, error output, stack trace, relevant git diff, and applicable spec or implementation notes. Failure analysis uses this evidence to produce a structured debug report with root cause, fix plan, and next-action recommendation.

Why does root-cause debugging classify causes into predefined categories?

Classifying causes into predefined categories enables structured remediation and escalation. It ensures the debugging process generates a minimal, verifiable fix plan or an explicit escalation when human decisions are required for the failure.