菜单
Use this to inspect long-running tasks the user dispatched to this machine through Foolfad. This is relevant when asks about dispatched task status, dispatched task logs or output, whether a related command is still alive, or what branch/worktree a dispatched run used.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to run a long or resource-heavy task on another computer so their local machine stays free, the work continues if they close their laptop or lose connection, and the result returns as a reviewable branch in their project. Use this skill also when no offload target exists yet and the user needs help setting one up.
Use for dispatching a command from the current git repo to a remote machine in order to offload work for execution.
Clone GitHub repos on this machine with ghwc: canonical owner/repo casing, shared bare clone, branch-named sibling worktrees under ~/Projects.
Use this skill for any task involving the ambit CLI: creating or destroying private networks, deploying apps to a private network, checking network or router health, listing routers, diagnosing connectivity problems, managing app secrets, or streaming app logs. Trigger phrases include "create a network", "set up ambit", "deploy with ambit", "ambit create", "ambit deploy", "ambit doctor", "check router status", "destroy a network", "managing app secrets", "streaming app logs", and similar.
Use when inspecting state, output, completion, or worktree activity for Codex goal runs launched by Boondoggle.
Use when launching a persistent Codex goal run with `boondoggle` from a prompt on stdin.
| name | foolfad-target |
| description | Use this to inspect long-running tasks the user dispatched to this machine through Foolfad. This is relevant when asks about dispatched task status, dispatched task logs or output, whether a related command is still alive, or what branch/worktree a dispatched run used. |
You are on the machine where the dispatched command runs. Inspect local files and processes directly, then answer with the concrete state you found.
Foolfad launches a command on this machine using a bare repo and worktree layout. The source branch is pushed first, then the run branch is pushed as:
foolfad/<run-id>
Default target paths are:
~/.remote-work/repos/<repo-path>/.bare
~/.remote-work/repos/<repo-path>/foolfad-<run-id>
Useful environment names: FOOLFAD_REPO_PATH, FOOLFAD_REMOTE_ROOT, FOOLFAD_WORKTREE_DIR, and FOOLFAD_RUN_BRANCH.
List recent Foolfad worktrees under the remote root:
root="${FOOLFAD_REMOTE_ROOT:-${HOME}/.remote-work}"
find "$root/repos" -path '*/.git' -not -path '*/.bare/*' -printf '%T@ %h\n' 2>/dev/null \
| sort -nr \
| head -20
Inspect the selected worktree:
worktree="${HOME}/.remote-work/repos/gh/OWNER/REPO/foolfad-run-id"
git -C "$worktree" status --short --branch
git -C "$worktree" log -1 --oneline
Check recent file activity in a selected worktree:
find "$worktree" -xdev -type f -printf '%T@ %p\n' 2>/dev/null \
| sort -nr \
| head -40
Look for a process tied to that worktree:
pgrep -af "$worktree" || true
ps -eo pid,ppid,etime,stat,cmd --sort=etime | rg -F "$worktree" || true
When working locally in the source repo, these commands often identify the Foolfad run branch or pushed state:
git branch --list 'foolfad/*'
git log --all --decorate --oneline --grep='Codex Goal Worktree State' -20
git remote -v
Foolfad itself runs commands like:
foolfad -- npm run dev
foolfad --command 'npm run test'
Foolfad writes the pushed repo state to a local worktree on this machine and runs the requested command there. It does not create a standard log file or pidfile. If logs are not present as files, say so and report process state, worktree status, last commit, and recent file activity instead.
If the command is a Boondoggle run and the boondoggle-runs skill is available, use that skill for Boondoggle-specific activity and completion signals.