laneslisted

Start, restart, stop, and check loop lanes as named background Claude Code sessions seeded from canonical prompt files, the scripted replacement for the manual morning refresh (cancel loop, clear, re-paste the canonical prompt) across N lanes on a machine. `start`/`restart` first pull the repo and refresh the plugin marketplace, then launch each configured lane with its per-lane model/effort. `consume-restarts` reads each configured lane's telemetry `restart_request` and relaunches the stopped lanes that asked, the scheduled headless reader. Use when: 'launch my lanes', 'restart the loop lanes', 'start the work lanes', 'morning lane refresh', 'stop a lane', 'which lanes are running', 'lane status', 'consume restart requests', 'lane restart consumer', 'relaunch the lanes that asked'. Mutating and operator-initiated; never touches a session whose name is not a configured lane.
melodic-software/claude-code-plugins · ★ 15 · AI & Automation · score 73

Install: claude install-skill melodic-software/claude-code-plugins

## Repository context. Gather first Collect these with **individual** Bash calls, one command per call, never combined into a single invocation: - Repo root, `git rev-parse --show-toplevel` Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls rather than pre-compute lines: the harness runs a skill's whole pre-compute block as one shell invocation, and a worktree-isolated session refuses a compound command that contains git. ## Pre-computed context claude CLI: !`claude --version 2>/dev/null || echo "MISSING (required)"` jq: !`command -v jq >/dev/null 2>&1 && echo "present" || echo "MISSING (required)"` Lane config: !`bash "${CLAUDE_PLUGIN_ROOT}/skills/lanes/scripts/probe-lane-config.sh" 2>/dev/null || echo "unknown"` ## Variables Arguments: `$ARGUMENTS` ## Purpose Running N loop lanes on a machine means a daily ritual: for each lane, cancel its loop, clear, and re-paste its canonical prompt. This skill collapses that to one command. `start`/`restart` pull the repo and refresh the plugin marketplace once, then launch each configured lane as a **named background session** seeded from the lane's canonical prompt file, mirroring that lane's model/effort onto the launch. `status`/`stop` read and manage those sessions through the CLI's own background-session surface. **Owns only its own lanes.** `stop`/`restart` act on a session **only** when its name is a lane in the resolved config, a hand-started se