← ClaudeAtlas

workflowlisted

Run Pitbox slot work or integrate ready slots. Use when working in a Pitbox slot, starting a parallel task with Pitbox, continuing a slot conversation after ready, or when the user explicitly asks to collect ready slots. Ordinary single-task work in the main checkout follows the repository's normal workflow.
WarLikeLaux/pitbox · ★ 0 · AI & Automation · score 67
Install: claude install-skill WarLikeLaux/pitbox
# Pitbox workflow Pitbox has two modes. Use the Pitbox MCP tools when available, passing the absolute repository or worktree path as `repo`. The CLI provides the same commands. Read `pitbox guide` if the pool is unfamiliar. Pitbox never edits `AGENTS.md`. Read it for project checks and deployment commands. ## Slot mode Use this mode for a task in a Pitbox worktree. The main checkout belongs to the integrator while parallel tasks run. Start a new task with `pitbox status`, then `pitbox claim` without a slot number. Claim atomically chooses a free slot and reports its path. Work in that path. Do not ask the user to pick a slot. If there are no slots yet, run `pitbox setup`. If all existing slots are busy, report that rather than creating more slots without a request. Run relevant checks, commit only this task's files, and call `pitbox ready <slot>`. A ready marker records the exact commit for handoff. It never starts collection or deployment. For visual work, capture a screenshot from the local preview and display the image in the result. A localhost link is not a screenshot. Do not wait for visual acceptance before committing and marking ready. The user's selection of Pitbox slot work places repository deploy-before-commit and visual acceptance steps at integration. The slot agent does not deploy, collect, or push the main branch. Push the task branch only if `.pitbox/config` sets `REQUIRE_PUSH=1`. The user may continue in the same conversation. Feedback on the same read