skills.rest
kagenti
kagentiOFFICIAL
Explore all skills by this author →
GitHub

rca:kind

Automate root cause analysis of failures in local Kind Kubernetes clusters.

292|103|Updated Mar 27, 2025
Search Tags:#ci/cd#debugging#root cause analysis#kubernetes#e2e testing#kind
One-click install
npx skills add https://github.com/kagenti/kagenti --skill rca-kind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rca:kind
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/rca%3Akind
Command: npx skills add https://github.com/kagenti/kagenti --skill rca-kind

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured workflow to diagnose and resolve failures occurring within local Kind Kubernetes clusters, streamlining the debugging process for developers.

Core Features & Use Cases

  • Reproduce Failures: Quickly set up a local Kind cluster to replicate CI or local test failures.
  • Inspect Cluster State: Gather detailed information about pods, events, and logs from the cluster.
  • Diagnose Root Causes: Analyze logs from key components like Kagenti UI and Ollama to pinpoint issues.
  • Fix and Verify: Implement fixes and re-run specific tests to confirm resolution.
  • Use Case: A local end-to-end test for a new agent deployment fails. Use rca:kind to reproduce the failure in a local Kind cluster, inspect the deployed agent's logs, identify a misconfiguration, correct it, and re-run the test.

Quick Start

Use the rca:kind skill to debug a failed local Kind cluster test by reproducing the failure and inspecting the cluster state.

Frequently Asked Questions about rca:kind

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

FAQPage Schema
How do I debug a failed Kind cluster test locally?▼

Debug a failed Kind cluster test by using a guided workflow to reproduce the failure, inspect the cluster state, diagnose root causes from pod logs, and verify the resolution by re-running the test.

What is the best way to reproduce CI failures in a local Kubernetes cluster?▼

Reproduce CI failures locally by setting up a local Kind Kubernetes cluster to replicate the exact test environment, allowing you to inspect pods, events, and logs to pinpoint the issue.

Can I run root cause analysis on a Kind cluster without causing conflicts with other sessions?▼

Yes, you can run root cause analysis safely because the process implements a cluster concurrency guard to prevent conflicts with other active sessions and redirects all diagnostic command outputs to files.

How do I diagnose issues with local agent deployments in a Kind environment?▼

Diagnose local agent issues in a Kind environment by inspecting the cluster state and analyzing detailed logs from key components like Kagenti UI and Ollama to identify misconfigurations.

Does the Kind debugging workflow support verifying fixes for failed E2E tests?▼

Yes, the Kind debugging workflow supports verifying fixes by allowing you to implement corrections and re-run specific end-to-end tests to confirm the failure has been fully resolved.

Related Skills

Explore More Software Engineering Skills→
kagentikagenti
292

tdd:kind

Orchestrate a local Kind Kubernetes cluster for Kagenti test-driven development.

Official
Advanced
mnthemnthe

debug

Guide systematic debugging workflows to reproduce, analyze, fix, and verify errors.

Community
Basic
sqfzysqfzy

fix

Trace root causes, implement fixes, and validate with regression tests.

Community
Advanced
incidentfoxincidentfox
654

kubernetes-debug

Diagnose Kubernetes pod issues using events, logs, and pod descriptions.

Official
Intermediate