debug-buttercup
All pods run in namespace crs. Use when pods in the crs namespace are in CrashLoopBackOff, OOMKilled, or restarting, multiple services restart simultaneously (cascade failure), or redis is unresponsive or showing AOF warnings.
Profile →npx skills add sickn33/agentic-awesome-skills --skill debug-buttercup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Debug Buttercup ## When to Use - Pods in the `crs` namespace are in CrashLoopBackOff, OOMKilled, or restarting - Multiple services restart simultaneously (cascade failure) - Redis is unresponsive or showing AOF warnings - Queues are growing but tasks are not progressing - Nodes show DiskPressure, MemoryPressure, or PID pressure - Build-bot cannot reach the Docker daemon (DinD failures) - Scheduler is stuck and not advancing task state - Health check probes are failing unexpectedly - Deployed Helm values don't match actual pod configuration ## When NOT to Use - Deploying or upgrading Buttercup (use Helm and deployment guides) - Debugging issues outside the `crs` Kubernetes namespace - Performance tuning that doesn't involve a failure symptom ## Namespace and Services All pods run in namespace `crs`. Key services: | Layer | Services | |-------|----------| | Infra | redis, dind, litellm, registry-cache | | Orchestration | scheduler, task-server, task-downloader, scratch-cleaner | | Fuzzing | build-bot, fuzzer-bot, coverage-bot, tracer-bot, merger-bot | | Analysis | patcher, seed-gen, program-model, pov-reproducer | | Interface | competition-api, ui | ## Triage Workflow Always start
- When to Use
- When NOT to Use
- Namespace and Services
- Triage Workflow
- Historical vs Ongoing Issues
- Cascade Detection
- Log Analysis
- Resource Pressure
- Redis Debugging
- Queue Inspection
- Health Checks
- Telemetry (OpenTelemetry / Signoz)
- Volume and Storage
- Deployment Config Verification
kubectl get pods -n crs -o wide
kubectl get events -n crs --sort-by='.lastTimestamp'
kubectl get events -n crs --field-selector type=Warning --sort-by='.lastTimestamp'
Why did a specific pod restart? Check Last State Reason (OOMKilled, Error, Completed)
kubectl describe pod -n crs <pod-name> | grep -A8 'Last State:'
Check actual resource limits vs intended
kubectl get pod -n crs <pod-name> -o jsonpath='{.spec.containers[0].resources}'
Crashed container's logs (--previous = the container that died)
kubectl logs -n crs <pod-name> --previous --tail=200
Current logsWhat does the debug-buttercup skill do?
All pods run in namespace crs. Use when pods in the crs namespace are in CrashLoopBackOff, OOMKilled, or restarting, multiple services restart simultaneously (cascade failure), or redis is unresponsive or showing AOF warnings.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill debug-buttercup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.