メニュー
Create an isolated git worktree in a new tmux window via `just wt new`. Use when the user asks to use, create, spin up, or work in a worktree in a jolo container.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Extract clean Markdown from web pages via the self-hosted Crawl4AI service at $CRAWL4AI_URL. Use when WebFetch returns junk on JS-rendered or anti-bot pages, or for whole-site ingestion. Keyless — never install a crawler, puppeteer, or hosted Firecrawl.
Prioritize open TODO items by effort and impact, recommend what to work on next. Add the `full` keyword to also weigh project notes and stash context.
Browse, screenshot, or visually verify a local web app using the pre-installed browser-check and playwright-cli (never install your own browser). Use when asked to screenshot, browse, open/view a page, check the UI, or confirm the site is running.
Resume a session — read the paste-back handoff note to recall what we last worked on, falling back to a git+TODO status when none exists. Add the `full` keyword to also deep-scan project notes and memory.
Write the paste-back handoff note (scratch/resume-session.md) so the next session can hit the ground running. Add the `full` keyword to also save durable knowledge to denote notes + TODO and commit.
Get oriented on host-level, cross-project knowledge by reading the stash README map. Use when starting fresh in a container, or when you need the lay of the land for hardware, dotfiles/preferences, Emacs, Linux, or cross-project conventions that live outside the current repo.
| name | j-worktree |
| description | Create an isolated git worktree in a new tmux window via `just wt new`. Use when the user asks to use, create, spin up, or work in a worktree in a jolo container. |
When the user asks to use / create / spin up a worktree, run the in-container
wt manager — it makes the git worktree AND a tmux window in one step. Do NOT
hand-roll git worktree add or tmux new-window.
The launched claude starts CLEAN, but it is a full checkout: it auto-loads
AGENTS.md/CLAUDE.md and SessionStart hooks, and has docs/TODO.org,
docs/notes/, and PROJECT.org right there. So the task context is already
written up. Don't re-state it in -p — the only thing the agent is missing is
WHICH item to work on. Point at it:
just wt new [name] -p "Work the TODO '<heading>' in docs/TODO.org: read its body
and linked notes, mark it INPROGRESS, then implement."
-p "..." is what launches claude (wt runs claude <prompt>). WITHOUT it
the window is a bare shell and no agent starts — almost never wanted.[name]: use the name the user gave; if none, omit it and wt picks a random
adjective-noun (never invent one).--from <ref>: base the branch on <ref> instead of current HEAD.-p when it's genuinely one-off and small.A worktree branches off committed HEAD. If the task depends on UNCOMMITTED
changes in the main tree, they are NOT in the worktree. Commit them first (or
--from the right ref), or tell the user the worktree won't see them.
Result: worktree at .worktrees/<name> on new branch <name>, tmux window
wt-<name> in the dev session with claude running. Tell the user the window
name and that C-b w (or its number) jumps to it.
just wt ls — list worktree windowsjust wt sync [name] — rebase the worktree on main's branchjust wt land [name] [--rm] — merge it back into the current branchjust wt rm [name] — remove worktree + branch + windowWorktrees live under $WORKSPACE/.worktrees/ (bind-mounted, survives container
rebuilds). This is the jolo way — prefer it over using-git-worktrees here.