ship-autonomous

Automates branching, committing, PR creation, CI monitoring, and gated merging for GitHub pull requests.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill ship-autonomous-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-autonomous
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/git-agent/skills/ship-autonomous
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill ship-autonomous-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Shipping code involves a repetitive chain of manual steps — branching, verifying tests and lint, committing, opening a PR, watching CI, responding to review comments, and merging — each of which can silently fail or be done unsafely. This Skill runs that entire pipeline autonomously with hard guardrails, so a red tree is never committed and a merge never lands on anything but green checks. ## Core Features & Use Cases - End-to-end ship pipeline: Chains pre-flight guards, branch creation, test/lint/browser verification, delegated commits, PR creation, and CI watching into one workflow. - Bounded CI autofix: Classifies failing checks (lint, typecheck, peer-deps, external blockers) and applies only allow-listed fixes, capped at 3 attempts per check before escalating. - Event-driven PR monitoring: Subscribes to PR webhook events (or polls as fallback), triages review comments by severity, and gates merging behind explicit user approval pinned to the verified commit. - Use Case: You finish a feature and ask the agent to ship it. It runs your tests, opens the PR, watches CI overnight, fixes a lint failure, replies to a review bot's comment, and asks you for approval before squash-merging. ## Quick Start Ask the agent to autonomously ship the current changes and watch the PR until it is ready to merge.

Frequently Asked Questions about ship-autonomous

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

FAQPage Schema
How do I automatically create and merge a GitHub pull request with CI checks?▼

Invoke the ship pipeline, which branches from the default branch, runs tests and lint, commits, opens a PR via the GitHub CLI, then watches CI checks. Merging only happens after all checks pass and you explicitly approve via a confirmation prompt.

How does the skill handle failing CI checks on a pull request?▼

It fetches the failing run log pinned to the PR's head commit, classifies the failure as lint, typecheck, peer-deps, or external-blocker, and autofixes only the allow-listed classes. Each check is capped at 3 fix attempts before escalating to the user.

Can it merge a PR without my approval?▼

No. Merging requires an explicit confirmation showing the PR URL, check summary, and review state. The merge is pinned to the verified head commit with --match-head-commit, and branch deletion requires its own separate approval.

What happens when tests or lint fail before committing?▼

The pipeline stops immediately and reports the failing output verbatim. It never commits a red tree, never runs watch-mode test scripts, and never applies lint --fix before the user has seen the diff.

Does it respond to pull request review comments automatically?▼

Yes. It classifies each finding as blocking or non-blocking, reproduces blocking defects before fixing them, replies with evidence when a finding is wrong, and escalates ambiguous or CHANGES_REQUESTED reviews to the user instead of guessing.

What are the limitations of the autonomous ship workflow?▼

It requires the GitHub CLI to be authenticated and works only inside the Claude Code environment with the git-agent plugin's commit and PR sub-skills. Unrecognized CI failures, ambiguous reviews, and external blockers like billing or token expiry always escalate rather than being auto-resolved.