ship-it

Automate test generation, linting, docs, and PR creation for main changes.

Updated Mar 22, 2026

Search Tags:#automation #git #testing #pr #ship #ci

Ready to run

npx skills add https://github.com/reedling78/chicago-transit-tracker --skill ship-it-reedling78

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/reedling78/chicago-transit-tracker/tree/main/.claude/skills/ship-it
Command: npx skills add https://github.com/reedling78/chicago-transit-tracker --skill ship-it-reedling78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the final delivery workflow by automating test generation, linting, documentation updates, branch creation, commits, pushes, and PR creation when you're ready to ship.

Core Features & Use Cases

Automated test generation for changed files in the web app (components, pages, and libraries).
Linting and docs updates to ensure code quality and up-to-date documentation.
End-to-end PR lifecycle: create a feature branch from main, commit with a descriptive message, push, and open a PR.
Useful when you finish a batch of changes on main and want to publish them with minimal friction.

Quick Start

Say "ship it" to automatically orchestrate tests, linting, docs updates, branch creation, commits, pushes, and PR creation.

Frequently Asked Questions about ship-it

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

FAQPage Schema

How do I automate git PR creation and testing in one step?▼

You can automate git PR creation by running a single command that generates tests, lints code, updates docs, creates a branch from main, commits, pushes, and opens the PR automatically.

What is the best way to ship code changes from main to a pull request?▼

The best way to ship code changes from main involves coordinating with git status and recent commits to identify changes, then automating branch creation, commits, pushes, and PR opening.

Can I automatically generate tests for changed files before opening a PR?▼

Yes, you can automatically generate tests for changed files in your web app, including components, pages, and libraries, ensuring tests and builds pass before opening a PR.

Does this automated shipping workflow update documentation and run linting?▼

Yes, the automated shipping workflow runs linting and updates documentation to ensure code quality and up-to-date docs before creating a feature branch and opening a pull request.

When should I use an automated PR workflow for my web app changes?▼

You should use an automated PR workflow when you finish a batch of changes on main and want to publish them with minimal friction by orchestrating tests, linting, docs updates, and PR creation.

What are the limitations of automating branch creation from main for PRs?▼

A key limitation is that branch creation is strictly from main, meaning the automated workflow applies to web app changes detected via git diff and may not suit complex branching strategies outside of main.