---
name: diagnose
description: Investigate cluster issues
aliases: [diag]
invokes: workflow:incidents/*
---

# /diagnose Command

Investigate and diagnose problems in the Raspberry Pi Kubernetes cluster.

## Usage

```
/diagnose <issue-description>
/diagnose pod <pod-name> -n <namespace>
/diagnose app <argocd-app-name>
/diagnose node <node-name>
```

## What It Does

Invokes the k8s-orchestrator to coordinate multiple specialist agents for investigation. May trigger incident workflows:

- `pod-crashloop` - For CrashLoopBackOff issues
- `node-issue-response` - For node problems
- `resource-pressure-response` - For resource alerts
- `argocd-sync-failure` - For sync failures

## Diagnosis Types

### General Issue
```
/diagnose "my app is returning 503 errors"
```

### Pod Diagnosis
```
/diagnose pod myapp-7d9f8b6c5-x2k4m -n production
```

### ArgoCD App Diagnosis
```
/diagnose app homepage
```

### Node Diagnosis
```
/diagnose node pi5-1
```

## Output Format

```
Diagnosis for: [issue description]
Status: [Investigating/Identified/Resolved]

Findings:
1. [Finding with evidence]

Root Cause:
[Explanation]

Recommended Actions:
- [SAFE] Action that can be auto-applied
- [CONFIRM] Action requiring approval
- [INFO] Suggestion for manual follow-up

Severity: [Low/Medium/High/Critical]
```

## Options

- `--verbose` - Include full command outputs
- `--logs` - Focus on log analysis
- `--metrics` - Focus on metrics analysis
- `--quick` - Fast surface-level check only