ship

Enforce validation pipelines and quality gates before shipping code changes.

Updated Aug 23, 2026

Search Tags:#commit #validation #shipping #ci-cd #code-review #quality-gates #pull-request

Ready to run

npx skills add https://github.com/LeviLeckenby/agentic-ways-of-working --skill ship-levileckenby

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/LeviLeckenby/agentic-ways-of-working/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/LeviLeckenby/agentic-ways-of-working --skill ship-levileckenby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship changes for deployment by enforcing mandatory validation gates before commit/push/PR, ensuring code quality and security.

Core Features & Use Cases

Mandatory Validation Pipeline: guarantees code changes are reviewed and security-audited prior to completion.
Automated pre-flight & gates: runs tests, linting, and type checks in parallel, and checks for secrets.
Commit & PR workflow: guides composition of commits and creation of pull requests with verification details.
Post-ship hygiene: summarizes validation status and updates tracking after shipping.

Quick Start

Run Ship to validate changes, commit the results, and open a pull request after all gates pass.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I enforce mandatory validation checks before a git commit or pull request?▼

Quality gates are automated pre-flight checks that run tests, linting, type checks, and secret detection in parallel before code changes are pushed. They guarantee code is security-audited and reviewed prior to commit completion.

What's the best way to automate pre-commit hooks for security audits and linting?▼

The best way to automate pre-commit security audits and linting is using a strict validation pipeline that checks for secrets and runs quality gates in parallel. This guarantees changes are reviewed before shipping to a pull request.

Does this validation pipeline work with multi-agent team collaborations?▼

Yes, this validation pipeline applies to software development workflows requiring pre-push checks and code reviews across multi-agent team collaborations. It enforces structured commit and pull request guidance with verification details for all contributors.

How do I structure a pull request with automated pre-merge validation results?▼

To structure a pull request with pre-merge validation results, run automated tests and security audits first, then compose commits with the generated verification details. This ensures tracking is updated and validation status is summarized post-ship.

What happens if automated type checks or secret detection fails during pre-push?▼

If automated type checks or secret detection fail during pre-push, the strict quality gates block the changes from shipping. The mandatory validation pipeline must pass completely before a commit is finalized or a pull request is opened.