auto-ship

What problem does it solve?

It eliminates the manual coordination needed to continuously drain a GitHub Projects To Do lane, resolve dependencies, dispatch build agents, and safely merge only the resulting green PRs.

Core Features & Use Cases

• Autonomous board orchestration: Watches the project’s To Do lane and repeatedly advances cards through In Progress → In Review → Done using dependency readiness derived from the board.
• Parallel build dispatch with safety limits: Runs up to a configurable number of tasks in flight (default 3) via background yolo-ship agents, while keeping merge operations serialized.
• Crash-safe, resumable loop: Reconciles orphaned in-flight cards on run start by checking PR ground truth and returns stranded work to the correct lane.
• Human escalation when decisions are required: Routes underspecified or human-blocked cards to Needs Input with fill-in-the-blank questions, preventing dead-ends in autonomous execution.
• Special walk lane handling: Detects (walk)-tagged cards and drains them via a serialized k8s acceptance loop rather than code shipping.
• Live observability on the board: Maintains per-card progress heartbeats and a durable local journal for failure signatures and loop prevention.

Quick Start

Ask the assistant to run auto-ship to drain the project-ax “TO DO” lane by watching for changes and continuously shipping all dependency-satisfied cards until the board stops changing.