ship

Automate type checks, tests, and safe git commits before pushing releases.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/wtyler2505/ProtoPulse --skill ship-wtyler2505
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/wtyler2505/ProtoPulse/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/wtyler2505/ProtoPulse --skill ship-wtyler2505

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely shipping code requires strict validation to prevent broken builds and failed deployments; this Skill automates a pipeline that enforces type checks, test runs, and safe git operations to abort on any failure.

Core Features & Use Cases

  • End-to-end pipeline: Type check, run tests, stage changes, commit with a safe message, and push.
  • Safety-first: Aborts on type or test failures and on risky changes, preventing bad releases.
  • Use Case: You’re preparing a release branch and need to guarantee all checks pass before merging.

Quick Start

Invoke /ship with an optional message to run the full pipeline and safely push changes only after all checks pass.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git commits to abort on type check or test failures?

Automated shipping pipelines enforce type checks and test runs before staging and committing changes, aborting the entire process automatically if any validation fails to prevent faulty releases.

What is the best way to safely push feature branch changes after running checks?

The safest way to push feature branches is running an end-to-end pipeline that executes type checks and tests, then stages and commits changes with a safe message only if all validations pass.

Does this automated release pipeline work for hotfix patches?

Yes, the automated release pipeline applies to hotfix patches by enforcing deterministic checks and guarded commits, ensuring every patch change is validated before being pushed to the repository.

How do I prevent broken builds when preparing a release branch?

Prevent broken builds by running a safety-first pipeline that applies deterministic type checks and tests, aborting on any failure or risky changes before a guarded commit is allowed to proceed.

Can I run a full type check and test pipeline without manual git operations?

Yes, you can invoke the full pipeline to automatically run type checks, execute tests, stage changes, commit with a safe message, and push, eliminating the need for manual git operations.

When should I not use an abort-on-failure git commit pipeline?

You should not use an abort-on-failure pipeline when you need to stage or commit changes that are intentionally incomplete, as the strict type check and test validation will halt the process on any failure.