Menu
File a specific clud improvement, feature request, bug report, or rough-edge report as a GitHub issue against zackees/clud; ask for details only for a bare manual /clud-improve invocation without an argument string.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
File a deeply-researched GitHub issue via investigate → investigate → post, returning a summary plus the issue URL. Files without asking for confirmation.
Spin up a fast Linux build container for a Rust + soldr + zccache, Python (uv), or C++ (CMake + ccache) project using the bundled `docker-build` tool family. Uses anonymous Docker volumes for build state and a read-only bind for source — the one rule that turns Docker-Desktop's 20-minute cold-build into a sub-30-second warm cycle.
Diagnose and recover a wedged Docker Desktop (engine pipe/socket absent while the UI stays alive, WSL/Docker startup failures) and answer Docker VM disk-growth / memory-pressure questions. Read-only `doctor` first; every restart/reset is confirmation-gated and preserves images/volumes; storage disks are resolved from Docker Desktop's real config (never assumed) and never compacted or deleted automatically.
Coordinate dependent cross-repo changes under a repo-local .extern-repos/ checkout convention.
Show a git diff in a native OS webview window (Beyond Compare-style dual-pane with file picker on the left) via the bundled git/clud-git-diff.py tool. Invoke when the user asks to visually review changes between revisions.
Worktree, branch, process-audit, and quarantine playbook extracted from /clud-pr so /clud-fix-quick and other skills can reuse it. Use this when the user asks for worktree cleanup, stale-branch teardown, or a process audit on a leftover dir.
| name | clud-improve |
| description | File a specific clud improvement, feature request, bug report, or rough-edge report as a GitHub issue against zackees/clud; ask for details only for a bare manual /clud-improve invocation without an argument string. |
| triggers | ["When the user types \"/clud-improve <specific report>\"","When the user wants to suggest a specific clud improvement, feature, bug, or rough edge","When an agent auto-selects this skill because the conversation already contains a concrete clud report"] |
Capture one specific improvement idea for clud and ship it as a GitHub issue against zackees/clud.
Three hard rules:
/clud-improve with no argument string and no concrete report in the current request, ask exactly: how can clud improve? be as specific as possible. Wait for the answer before continuing.gh auth status, post directly with gh issue create --repo zackees/clud, and return the issue URL. If auth fails, tell the user to run gh auth login and stop.This skill does not change code; it files an improvement request against zackees/clud. If the resulting work is a bug fix or feature, that downstream PR must follow RED -> GREEN via /clud-pr: a focused failing test before the implementation that turns it green.
/clud-improve <text>, use <text> as the report./clud-improve without details, ask exactly how can clud improve? be as specific as possible and wait.gh auth status. If it exits non-zero or reports not logged in:
gh auth login and re-run /clud-improve."feat: <short summary>, fix: <short summary>, or chore: <short summary>. Body sections:
clud --version, OS, relevant file paths). Do not invent.gh issue list --repo zackees/clud --search "<keywords>" --state all. Flag only genuine overlap (same component + same intent). Weak keyword matches do not count.gh issue create --repo zackees/clud --title "..." --body "$(cat <<'EOF' ... EOF)". Use a heredoc so formatting survives.gh auth status fails, stop. Do not open a browser, web form, or file to a different repo.zackees/clud. Do not infer the repo from the working directory; this skill is specifically for upstream clud feedback.gh issue create./clud-issue instead.