reliability-engineer

Diagnoses VM, Terraform, and CI failures and reports root-cause hypotheses without applying fixes.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill reliability-engineer-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reliability-engineer
Source: https://github.com/lfuuu/claude-rules/tree/main/shared-skills/roles/reliability-engineer
Command: npx skills add https://github.com/lfuuu/claude-rules --skill reliability-engineer-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When VMs become unhealthy, Terraform state drifts, or CI tests flake repeatedly, engineers waste hours hunting through logs and system state. This Skill performs read-only diagnostics across KVM hosts, VMs, Terraform state, and CI artifacts, then returns an evidence-backed root-cause hypothesis and routes the fix to the right specialist agent. ## Core Features & Use Cases - Read-only diagnostics: Collects logs (journalctl, docker logs), system state (pf vm check, virsh list, terraform plan), and metrics (df, free, ss) without mutating anything. - Known-pattern matching: Maps symptoms to a catalog of documented failure patterns such as Terraform state drift, non-idempotent Ansible roles, Nexus 503/404 mirror issues, etcd timeouts, and SSH agent timeouts. - Root-cause delegation: Routes each diagnosed issue to the appropriate agent (/platform-engineer, /devops, /ops-engineer, /qa-engineer) with a structured report including priority. - Use Case: A k8s-matrix CI run fails three times in a row on the same environment. The Skill analyzes past QA artifacts, identifies a common apt upstream timeout pattern, and delegates a Nexus mirror diagnosis plus an Ansible timeout fix. ## Quick Start Invoke the reliability-engineer skill with a description of the symptom, for example: diagnose why VM k8s-ha-alt-adp2 shows kubelet not ready after reapply.

Frequently Asked Questions about reliability-engineer

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

FAQPage Schema
How do I diagnose an unhealthy VM on a KVM host?

Run read-only checks such as pf vm check, virsh list, systemctl status, journalctl, and docker ps on the target VM. The Skill collects this evidence, matches it against known failure patterns, and returns a root-cause hypothesis with a delegation target.

How to detect Terraform state drift after manual changes?

Compare terraform plan output and pf vm list --virsh against the tfvars definitions. A mismatch, often caused by manual virsh destroy, indicates drift, which is then delegated to a platform engineer for targeted import or recreation.

Can this Skill fix the problems it finds?

No, it is strictly read-only and never applies fixes. It produces a diagnostic report with a root-cause hypothesis and delegates remediation to specialist agents such as platform-engineer, devops, or ops-engineer.

Why do k8s-matrix CI runs fail repeatedly on the same environment?

Repeated failures usually share a common symptom such as etcd startup timeouts or registry mirror timeouts. The Skill analyzes past QA artifacts across runs to detect the recurring pattern and identify the underlying cause.

What commands are allowed during infrastructure diagnostics?

Only read-only commands are permitted: virsh list and dominfo, systemctl status, journalctl, docker logs and ps, terraform plan, df, free, ss, and git log. Mutating commands like virsh destroy or terraform apply are blocked by hooks.