ks-diagnose

Diagnose system failures by collecting evidence and validating root-cause hypotheses.

118|10|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/heyallencao/KeyStore --skill ks-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ks-diagnose
Source: https://github.com/heyallencao/KeyStore/tree/main/execution/diagnose
Command: npx skills add https://github.com/heyallencao/KeyStore --skill ks-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers and engineers locate the root cause of system failures, tests, or abnormal behavior by guiding structured investigation and hypothesis testing.

Core Features & Use Cases

  • System Failure Analysis: Guides the user through collecting evidence such as logs, recent changes, and reproducing failures to pinpoint the underlying issue.
  • Hypothesis Formation and Validation: Assists in constructing and testing specific root-cause hypotheses based on gathered evidence.
  • Use Case: When a test fails unexpectedly, use this Skill to analyze logs, recent commits, and environment differences to identify the actual cause.

Quick Start

Provide the failing test output and relevant logs to diagnose the root cause effectively.

Frequently Asked Questions about ks-diagnose

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

FAQPage Schema
How do I find the root cause of a system failure or unexpected test failure?

To find the root cause of a system failure, you need to collect evidence like logs and recent commits, form specific hypotheses, and systematically validate them to pinpoint the underlying issue.

What is the best way to debug an abnormal system behavior when logs are unclear?

The best way to debug abnormal system behavior is through structured investigation: gather available evidence, construct potential root-cause hypotheses, and systematically test each one to validate the actual cause.

How does hypothesis validation work during system failure diagnosis?

Hypothesis validation in system failure diagnosis works by constructing specific root-cause assumptions based on gathered logs and evidence, then systematically testing each hypothesis to confirm or rule out potential causes.

Can I diagnose system failures without recent environment change data?

Diagnosing system failures without recent environment change data is possible but harder; the investigation prioritizes collecting logs, recent commits, and reproducing failures to form accurate root-cause hypotheses.

What are the limitations of hypothesis-driven debugging for complex system failures?

The limitation of hypothesis-driven debugging for complex system failures is its reliance on the quality of collected evidence; incomplete logs or irreproducible failures can prevent forming valid root-cause hypotheses.