Files
claude-code/commands/k8s/diagnose.md
OpenCode Test 431e10b449 Implement programmer agent system and consolidate agent infrastructure
Programmer Agent System:
- Add programmer-orchestrator (Opus) for workflow coordination
- Add code-planner (Sonnet) for design and planning
- Add code-implementer (Sonnet) for writing code
- Add code-reviewer (Sonnet) for quality review
- Add /programmer command and project registration skill
- Add state files for preferences and project context

Agent Infrastructure:
- Add master-orchestrator and linux-sysadmin agents
- Restructure skills to use SKILL.md subdirectory format
- Convert workflows from markdown to YAML format
- Add commands for k8s and sysadmin domains
- Add shared state files (model-policy, autonomy-levels, system-instructions)
- Add PA memory system (decisions, preferences, projects, facts)

Cleanup:
- Remove deprecated markdown skills and workflows
- Remove crontab example (moved to workflows)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-29 13:23:42 -08:00

1.5 KiB

name, description, aliases, invokes
name description aliases invokes
diagnose Investigate cluster issues
diag
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