docker-debugging
Docker container debugging and management. Use when investigating container issues, checking logs, resource usage, or Docker Compose services.
Works with
--- name: docker-debugging description: Docker container debugging and management. Use when investigating container issues, checking logs, resource usage, or Docker Compose services. license: Apache-2.0 --- # Docker Debugging ## Authentication Docker commands run directly via the Docker CLI. No API keys are needed - the Docker socket must be accessible in the sandbox environment. --- ## Available Scripts All scripts are in `.claude/skills/infrastructure-docker/scripts/` ### container_ps.py - List Containers ```bash python .claude/skills/infrastructure-docker/scripts/container_ps.py [--all] ``` ### container_logs.py - Get Container Logs ```bash python .claude/skills/infrastructure-docker/scripts/container_logs.py --container NAME_OR_ID [--tail 100] ``` ### container_inspect.py - Inspect Container ```bash python .claude/skills/infrastructure-docker/scripts/container_inspect.py --container NAME_OR_ID ``` ### container_stats.py - Resource Usage Statistics ```bash python .claude/skills/infrastructure-docker/scripts/container_stats.py [--container NAME_OR_ID] ``` ### image_list.py - List Docker Images ```bash python .claude/skills/infrastructure-docker/scripts/image_list.py [--filter "reference=myapp*"] ``` ### compose_ps.py - List Compose Services ```bash python .claude/skills/infrastructure-docker/scripts/compose_ps.py [--file docker-compose.yml] [--cwd /path] ``` ### compose_logs.py - Get Compose Service Logs ```bash python .claude/skills/infrastructure-docker/scripts/compose_logs.py [--services "api,db"] [--tail 100] ``` --- ## Investigation Workflow ### Container Debugging ``` 1. List containers: container_ps.py --all 2. Check logs: container_logs.py --container <name> --tail 200 3. Check resources: container_stats.py --container <name> 4. Inspect config: container_inspect.py --container <name> ``` ### Docker Compose Debugging ``` 1. Check services: compose_ps.py 2. Check logs: compose_logs.py --services "api,worker" --tail 100 ``` --- ## Anti-Patterns to Avoid 1. **Never run destructive commands** without explicit user approval (docker rm, docker rmi, docker system prune) 2. **Always use --tail** for logs to avoid overwhelming output 3. **Check container status first** before trying to exec into it
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

