Development: Cleanup and maintenance for the development environment. Removes build artifacts, caches, containers, and recovers disk space. Run from repository root with 'just clean'. Use when developers need to free disk space or reset the build environment.
/plugin marketplace add atrawog/bazzite-ai-plugins/plugin install atrawog-bazzite-ai-dev-bazzite-ai-dev@atrawog/bazzite-ai-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
The clean development commands remove build artifacts, caches, containers, and other temporary files to recover disk space and reset the development environment.
Key Concept: This is a development command - run with just from the repository root, not ujust. It provides both interactive menu and non-interactive modes.
| Action | Command | Description |
|---|---|---|
| Interactive menu | just clean | Show cleanup options |
| Status report | just clean status | Show what would be cleaned |
| Safe cleanup | just clean all | Safe cleanup (preserves running containers) |
| Nuclear cleanup | just clean nuke | NUCLEAR: destroy everything (requires NUKE confirmation) |
| Podman prune | just clean podman | Full podman system prune |
| Images | just clean images | Dangling images only |
| All images | just clean images all | All unused images |
| Build cache | just clean images build-cache | Podman builder cache |
| Containers | just clean containers | Stopped containers |
| Runners | just clean runners | Stop/restart GitHub runners |
| VMs | just clean vm | VM images (libvirt + cache) |
| System | just clean system | Tmp files + journal |
| Logs | just clean logs | Remove *.log files |
| Docs | just clean docs | Remove site/ directory |
| Output | just clean output | Remove output/ contents |
| Cache menu | just clean cache | Cache cleanup submenu |
| Pixi cache | just clean cache pixi | .pixi/ + ~/.cache/rattler |
| Venv | just clean cache venv | venv/ directory |
| Chunkhound | just clean cache chunkhound | .chunkhound/ directory |
| Pip | just clean cache pip | ~/.cache/pip/ |
| Pre-commit | just clean cache precommit | ~/.cache/pre-commit/ |
| GitHub CLI | just clean cache gh | ~/.cache/gh/ |
just clean all)Safe cleanup that preserves running containers and configurations:
Use when: You want to free disk space but keep your pod configurations intact.
just clean nuke)DESTROYS EVERYTHING - requires typing 'NUKE' to confirm:
Use when: You want a completely fresh start or are troubleshooting persistent issues.
Warning: This will delete:
just clean [ACTION] [SUBOPTION]
| Parameter | Values | Description |
|---|---|---|
ACTION | See quick reference | Cleanup action |
SUBOPTION | Varies by action | Sub-action for nested menus |
Show what would be cleaned (dry-run):
just clean status
Reports:
Safe cleanup (15 steps):
just clean all
Nuclear option (requires NUKE confirmation):
just clean nuke
# Type 'NUKE' when prompted to confirm
Full podman system prune:
just clean podman
Removes:
Clean podman images:
just clean images # Dangling only
just clean images all # All unused
just clean images build-cache # Builder cache
Remove stopped containers:
just clean containers
Manage GitHub runners:
just clean runners stop # Stop runners
just clean runners start # Start runners
Clean VM images:
just clean vm # Interactive
just clean vm libvirt # Libvirt VMs
just clean vm cache # VM cache
System cleanup:
just clean system # Interactive
just clean system tmp # Clean /var/tmp
just clean system journal # Vacuum journal logs
Clean development caches:
just clean cache # Interactive
just clean cache pixi # .pixi/ + ~/.cache/rattler
just clean cache venv # venv/
just clean cache chunkhound # .chunkhound/
just clean cache pip # ~/.cache/pip/
just clean cache precommit # ~/.cache/pre-commit/
just clean cache gh # ~/.cache/gh/
# See what would be cleaned
just clean status
# Then decide what to clean
just clean podman
# Safe cleanup
just clean all
# Or targeted cleanup
just clean images all
just clean cache pixi
just clean output
# Clean all caches and build artifacts
just clean cache all
just clean output
just clean docs
# Reinstall dependencies
just docs-install
# Clean containers and images
just clean podman
# Then rebuild
just build
# Nuclear option - destroys everything
just clean nuke
# Type 'NUKE' to confirm
# Reconfigure everything from scratch
ujust jupyter config
ujust ollama config
| Target | Typical Size | Command |
|---|---|---|
| Podman images | 10-50GB | clean podman |
| Builder cache | 1-10GB | clean images build-cache |
| /var/tmp | 1-5GB | clean system tmp |
| Journal logs | 100MB-1GB | clean system journal |
| Pixi cache | 1-5GB | clean cache pixi |
| Output/ | 1-20GB | clean output |
Symptom: Cannot remove files in output/ or /var/tmp
Fix:
# Fix permissions
sudo chown -R $USER:$USER output/
# For /var/tmp
sudo rm -rf /var/tmp/buildah*
Symptom: Images still present after prune
Cause: Containers referencing images
Fix:
# Stop and remove all containers first
just clean containers
just clean runners stop
# Then prune
just clean podman
Symptom: Runners fail to start after cleanup
Cause: Configuration lost or token expired
Fix:
# Re-authenticate
just gh-login
# Reconfigure runners
ujust runners config <REPO_URL> 1
pods (build pods), vms (build VMs), docs (build docs)ujust runners (runner management)just clean statusUse when the user asks about:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.