ship-loop

Advance the next ready Shipwright task through development, review, patching, and deployment.

9|2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/app-vitals/shipwright --skill ship-loop-app-vitals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-loop
Source: https://github.com/app-vitals/shipwright/tree/main/.claude/skills/ship-loop
Command: npx skills add https://github.com/app-vitals/shipwright --skill ship-loop-app-vitals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps Shipwright moving by automatically advancing the next ready task through development, review, patching, and deployment without manual coordination.

Core Features & Use Cases

  • Queue Draining: Repeatedly picks the highest-priority work item and advances it one pipeline step at a time.
  • Autonomous Delivery: Supports end-to-end repo operations such as opening PRs, applying fixes, reviewing patches, and merging or deploying when ready.
  • Operational Safety: Uses cheap prechecks, backoff, and resumable state so it can run continuously or stop cleanly once the queue is empty.

Quick Start

Use the ship-loop skill to autonomously drain the Shipwright queue and keep the next ready task moving through dev, review, and deploy.

Frequently Asked Questions about ship-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate my pull request and deployment workflow from a task queue?

Automating pull request and deployment workflows involves draining the Shipwright task queue, which advances the next ready item through development, review, patching, and deployment without manual coordination.

What is an autonomous delivery loop for GitHub repositories?

An autonomous delivery loop continuously picks the highest-priority work item and advances it one step at a time, handling PRs, fixes, and merges until the task queue is empty.

Do I need GitHub CLI authentication to run autonomous deployment loops?

Yes, autonomous deployment loops require GitHub CLI authentication along with repo-specific environment variables and task-store access to safely manage pull requests and deployments.

Can I continuously loop task deployments or run them as single-step executions?

Yes, task deployments support single-step execution or continuous looping under /loop, using gate-driven backoff and resumable state to safely resume work or stop cleanly when the queue is empty.

How does autonomous task queue draining handle operational safety and backoff?

Task queue draining uses cheap prechecks, gate-driven backoff, and resumable state to ensure operational safety, allowing continuous operation or a clean stop once the queue is empty.