kiro-doctor

Diagnose kiro plugin setup and report repo wiring, environment, and hook configuration issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-doctor-scapia-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-doctor
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-doctor
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-doctor-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When /kiro:* commands stop working, hooks fail to fire, or a fresh plugin install behaves unexpectedly, there is no easy way to tell what is misconfigured. This Skill runs a structured health check on a consumer's kiro plugin setup and turns raw check results into an actionable fix list. ## Core Features & Use Cases - Deterministic diagnostics: Runs a bundled doctor.mjs script that checks the .kiro/ directory layout, steering files, spec.json validity, node/python availability, and installed plugin hooks, printing a grouped PASS/WARN/FAIL/SKIP report. - Interpreted fix guidance: Translates each WARN/FAIL into a concrete remediation step, such as reinstalling the plugin, updating for the feedback-capture hook, or fixing a malformed spec.json. - Gradle build-health audit: On Gradle repositories, performs an advisory read-only audit of gradle.properties and build files to explain why impl RED/GREEN gates may be slow. - Use Case: After installing or updating the kiro plugin, run the doctor to confirm the repo is wired correctly, hooks resolve to real scripts, and the environment can execute the gate scripts. ## Quick Start Ask the AI to run the kiro doctor and verify that my kiro plugin setup is healthy and correctly wired.

Frequently Asked Questions about kiro-doctor

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

FAQPage Schema
How do I check if my kiro plugin is set up correctly?

Run the kiro-doctor skill, which executes a deterministic script checking the .kiro/ directory layout, steering files, spec.json validity, and installed hooks. It prints a grouped PASS/WARN/FAIL report and ends with a HEALTHY, USABLE, or NEEDS_ATTENTION verdict plus ordered fixes.

Why are my kiro hooks not firing after install?

The doctor checks whether each hook command resolves to a real script and whether the UserPromptSubmit hook is present. A missing UserPromptSubmit hook means the install predates the feedback-capture hook and needs a plugin update; unresolvable scripts indicate a partial install requiring reinstall.

Can the doctor verify that hooks actually run at runtime?

No. Hook firing is internal to Claude Code, so the doctor can only confirm hooks are correctly wired and their scripts resolve. It also cannot help if no /kiro:* commands appear at all, since that means the plugin is not installed or enabled.

What does the doctor check on Gradle repositories?

On repos with a build.gradle or build.gradle.kts, it runs an advisory audit of gradle.properties, build scripts, and the wrapper against performance checks like config-time token calls and test parallelism. The audit is read-only and never changes the overall health verdict.

Does kiro-doctor modify my repository files?

No. The skill is strictly read-only: it reports problems and instructs fixes but never edits repo files, steering, specs, or Gradle build files. All remediation steps are left for the user to apply.