Diagnose
Investigate and fix open issues in the .kiro/issues/ folder using test-first debugging. Use when asked to diagnose, triage, or work through unresolved bug reports, or when the user mentions open issues that need fixing.
Install
npx skills add aws-samples/sample-kiro-cli-multiagent-development --skill diagnosegit clone --depth 1 https://github.com/aws-samples/sample-kiro-cli-multiagent-development.git /tmp/sample-kiro-cli-multiagent-development
mkdir -p ~/.claude/skills
cp -r /tmp/sample-kiro-cli-multiagent-development/skills/diagnose ~/.claude/skills/diagnosePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Diagnose Issues ## When to Create Issue Docs Create a `.kiro/issues/YYYY-MM-DD-<slug>/` folder with `report.md` and `summary.md` when ANY of the following are true: - A bug is reported and fixed (by user, by tests, or discovered during review) - A production incident is investigated (even if the root cause is external) - A deploy fails and requires investigation beyond a simple retry - A smoke test fails and the fix is non-obvious - A review cycle finds critical issues that require code changes Do NOT create issue docs for: - Typos, formatting fixes, or trivial one-line changes - Review suggestions that are improvements, not bugs - Planned refactors that aren't fixing a broken behavior ## Diagnose Flow For each unresolved issue (folders in `.kiro/issues/` without a `summary.md`): 1. **Log the issue** — create `.kiro/issues/YYYY-MM-DD-<slug>/report.md` BEFORE starting the investigation. Include: one-line summary, impact (who/what is affected and severity), reproduction steps or error logs, and investigation notes as you work. 2. **Investigate** — read `report.md`, reproduce the problem, identify the root cause. Rule out false leads and record what was checked. 3. **Write a failing test** — create a test that captures the observed broken behavior. Run it to confirm it fails for the right reason. Do not skip this step — a fix without a regression test is incomplete.
Details
- Skill name
diagnose- Path
skills/diagnose/SKILL.md- License
- MIT-0
- Repo updated
- 9 September 2026
FAQ
What does the Diagnose skill do?
Investigate and fix open issues in the .kiro/issues/ folder using test-first debugging. Use when asked to diagnose, triage, or work through unresolved bug reports, or when the user mentions open issues that need fixing.
How do I install the Diagnose skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add aws-samples/sample-kiro-cli-multiagent-development --skill diagnose. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Diagnose popular?
It lives in aws-samples/sample-kiro-cli-multiagent-development, which has 43 GitHub stars and 9 forks.
Related skills
Agentcore Patterns
43aws-samples/sample-kiro-cli-multiagent-development
Verified Amazon Bedrock AgentCore patterns for Runtime handlers, Gateway MCP clients with SigV4/IAM auth, Memory session management with Strands, and Bedrock cross-region inference-profile IAM policies. Use when building or debugging AgentCore-based agents.
AWS Technical Docs
43aws-samples/sample-kiro-cli-multiagent-development
AWS technical documentation patterns covering procedures, lists, tables, titles, error messages, and content patterns. Use when writing AWS service documentation, procedures, troubleshooting guides, tutorials, or getting started content.
CLI Execution
43aws-samples/sample-kiro-cli-multiagent-development
CLI execution best practices covering RTK token compression, AWS discover-then-execute patterns, output control, and bash/zsh scripting with logging. Use when running CLI commands, querying AWS resources, writing automation scripts, or working with shell tooling.
Formal Verify Delivery Cycle
107Dimon94/skills
有界穷举检查 delivery-cycle 维护入口的时序与重试性质(R8 不写回旧周、R9 先读后写不盲重放、verified 必有回读、partial 不冒充 synchronized、R11 重跑零写入)。改动 skills/delivery-cycle/scripts/delivery-cycle.js 的执行、前读、写入、回读、时钟或结果判定代码,或改 tests/fake-adapters.js 时使用。
Customizing Vectors R
67jeremy-allen/claude-skills
Type-stable vector operations and custom vector classes using vctrs. Use this skill when building R packages with custom types, need guaranteed output types regardless of input values, implementing consistent coercion/casting rules, or creating vector classes that work seamlessly with data frames. Covers when to use vctrs vs base R, building custom vector classes, coercion methods, and testing vctrs classes.
Godot
46Randroids-Dojo/Godot-Claude-Skills
Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 for GDScript unit tests and PlayGodot for game automation and E2E testing. Supports web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.