ship

Lint, test, review, update Memory Bank, and commit code changes.

Updated Mar 1, 2026

Search Tags:#test #ship #lint #code-review #format #version-control #memory-bank

Ready to run

npx skills add https://github.com/haingt-dev/agent --skill ship-haingt-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/haingt-dev/agent/tree/main/global/skills/ship
Command: npx skills add https://github.com/haingt-dev/agent --skill ship-haingt-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lint, test, review, update Memory Bank, and commit changes with a single command to streamline release workflows and enforce consistency across projects.

Core Features & Use Cases

Pre-flight checks to verify clean state and safety constraints before shipping.
Lint/Format, Test, and Review steps to ensure code quality, followed by Memory Bank updates and Docs commits.
Stateless pipeline with deterministic step order and structured failure reporting for quick remediation.

Quick Start

Run /ship with a descriptive commit message to begin the shipping process.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate linting, testing, and committing code changes with one command?▼

You can automate the end-to-end shipping workflow by running a single command that lints, formats, tests, reviews, updates Memory Bank, and commits code changes in a deterministic step order.

What is a stateless shipping pipeline and how does it handle code review and formatting?▼

A stateless shipping pipeline executes pre-flight checks, formatting, testing, and code review in a strict deterministic sequence without retaining session state, ensuring consistent quality gates and structured failure reporting for quick remediation.

How do I prevent accidental commits during a rebase or in a detached HEAD state?▼

Automated shipping workflows apply safety checks to detect detached HEAD states and active rebase or merge conditions before executing any commits, preventing accidental changes to an unstable Git state.

Does the one-command shipping workflow validate conventional commit messages?▼

Yes, the shipping workflow includes conventional commit message validation during the commit step to ensure version control history adheres to standardized commit formats before finalizing changes.

What happens if linting or tests fail during the automated shipping process?▼

If linting, formatting, or tests fail, the pipeline halts execution and generates structured failure reporting, allowing developers to quickly identify and remediate the specific code quality issue.

Can I use an automated code shipping pipeline for projects requiring strict quality gates?▼

Yes, this automated pipeline is designed for software projects that require consistent quality gates, applying pre-flight state verification, linting, and testing before committing changes to version control.