From claude-code
Use when coordinating Claude Code background agents, `claude agents --json`, dispatched-session defaults, git worktrees, tmux/iTerm panes, resume/continue/from-pr/fork-session, session names and IDs, remote control, prompt suggestions, or cloud ultrareview runs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code:claude-agent-worktreesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for Claude Code session orchestration: background agents,
Use this skill for Claude Code session orchestration: background agents, worktrees, tmux/iTerm panes, resumes, PR-linked sessions, forked sessions, session names and IDs, remote control, prompt suggestions, and cloud ultrareview.
From this skill directory, the plugin root is ../...
Check command surface and current background sessions:
python3 ../../scripts/claude_code_inspector.py --commands agents ultrareview --json
claude agents --json
Use claude agents --json --all only when completed sessions are relevant and
the extra transcript/session metadata is needed.
Use claude agents for active background session state and dispatch defaults:
claude agents --json
claude agents --cwd /path/to/project --json
claude agents --model sonnet --permission-mode plan --add-dir /path/to/extra
Do not start or leave long-lived background sessions without a reason and a cleanup plan. Use explicit model, permission mode, settings, plugin-dir, and MCP config when reproducibility matters.
Use these root flags for session continuity:
claude --continue
claude --resume <session-id-or-search>
claude --from-pr <pr-number-or-url>
claude --fork-session --resume <session-id>
claude --session-id <uuid>
claude --name "display-name"
Prefer exact session IDs or PR URLs when the user wants a specific conversation. Use search/pickers only for interactive use.
Use worktrees when the task should be isolated from the current working tree:
claude --worktree
claude --worktree feature-name --tmux
claude --worktree feature-name --tmux=classic
Before creating worktrees, inspect git status and branch state. Do not create extra worktrees for tiny one-off commands unless isolation is the point.
Remote control, IDE, and Chrome integration are interactive surfaces:
claude --remote-control
claude --remote-control "session-name"
claude --ide
claude --chrome
claude --no-chrome
Use them only when the user asks for those integrations. Report how to stop or exit any interactive session started.
claude ultrareview is cloud-hosted and may consume time or quota. Run it only
when requested:
claude ultrareview
claude ultrareview main
claude ultrareview <pr-number-or-url> --json --timeout 30
Prefer local review or --print analysis for lightweight checks.
Report the current session/agent/worktree state inspected, exact command used, permission/tool settings, any created session/worktree/pane name, and cleanup or resume instructions when a process remains active.
npx claudepluginhub xopoko/plug-n-skills --plugin claude-codeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.