メニュー
Coordinate dependent cross-repo changes under a repo-local .extern-repos/ checkout convention.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
Wait for CI + CodeRabbit on the current PR, fix regressions and review comments, then merge to main.
| name | clud-extern-repos |
| description | Coordinate dependent cross-repo changes under a repo-local .extern-repos/ checkout convention. |
| triggers | ["When a task needs a dependent change in another repository","When the user asks to use .extern-repos for cross-repo work"] |
Use this workflow when the current repo needs coordinated work in a dependent repository.
If any parent or dependent repository change is a bug fix or feature implementation, use RED -> GREEN in that repository: write or identify the focused failing test/repro first, run it to fail, implement the scoped change, rerun it to pass, then run the broader repo checks before opening linked PRs.
Place each dependent checkout at <current-repo>/.extern-repos/<repo-name>/. Only immediate children of .extern-repos/ are tracked by clud GC.
Before cloning, verify .extern-repos/ is ignored by the current repo. If it is not ignored, ask before adding the ignore entry and refuse to create an unignored clone.
Create feature branches in the dependent repo with the same short-name style as clud-pr, for example feat/<short-name>.
Keep each repo's work scoped to that repo. Do not edit the parent repo from inside the dependent checkout, and do not edit the dependent checkout from the parent repo.
When opening PRs, link both directions:
Depends on <owner>/<repo>#<number>Coordinated with <owner>/<parent-repo>#<number>If the dependent PR must land first, make that ordering explicit in the parent PR body.
The daemon auto-removes .extern-repos/<name>/ once the directory has been inactive (no descendant mtime change) for at least 24 hours and no live clud session is rooted inside it. Anything tracked under .extern-repos/ is clud-managed by convention, so don't park work there that you want kept indefinitely — copy it elsewhere or commit + push it first.
Override the inactivity window via CLUD_GC_EXTERN_REPO_MAX_AGE_SECS (default 86400).