claude-autoship

Automate implementation, verification, review, and pull request creation from feature plans.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill claude-autoship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-autoship
Source: https://github.com/erclx/aitk/tree/main/claude/skills/claude-autoship
Command: npx skills add https://github.com/erclx/aitk --skill claude-autoship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the inconsistency and manual overhead of the post-planning phase by automating the transition from an approved feature plan to a verified, reviewed, and shipped pull request.

Core Features & Use Cases

  • Automated Pipeline: Chains implementation, verification, UI testing, and review into a single, recoverable session.
  • Safety Guardrails: Enforces strict stop conditions for critical failures, uncommitted changes, or missing plans to ensure code integrity.
  • Use Case: After a feature plan is approved, use this skill to automatically implement the changes, run tests, open a draft pull request, and capture durable patterns for future sessions.

Quick Start

Invoke the claude-autoship skill to execute the full post-plan pipeline for the current feature branch.

Frequently Asked Questions about claude-autoship

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

FAQPage Schema
How do I automate feature shipping from a plan to a pull request?

Automated feature shipping transitions an approved feature plan directly into a verified, reviewed pull request by chaining implementation, verification, UI testing, and PR creation into a single recoverable pipeline session.

What is the best way to automate post-planning software development workflows?

Automating post-planning workflows eliminates manual overhead by enforcing consistent shipping standards, applying safety guardrails like strict stop conditions for critical failures, and automatically capturing durable patterns for future sessions.

Do I need a feature plan file to automate pull request creation?

Yes, a valid feature plan file is required to automate pull request creation, serving as the mandatory input that triggers the automated implementation, verification, and review pipeline.

Does automated feature delivery work with git-based worktree management?

Yes, automated feature delivery requires git-based worktree management to ensure state recoverability and maintain branch alignment throughout the implementation, verification, and pull request creation pipeline.

What happens to automated CI/CD integration when there are uncommitted changes?

Automated CI/CD integration enforces strict safety guardrails that halt the pipeline when uncommitted changes are detected, ensuring code integrity and preventing inconsistent feature shipping.