pre-ship

Enforces sequential quality gates on staged changes before commit or push.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Elad73/agentic-base-layer --skill pre-ship-elad73
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-ship
Source: https://github.com/Elad73/agentic-base-layer/tree/main/global/skills/pre-ship
Command: npx skills add https://github.com/Elad73/agentic-base-layer --skill pre-ship-elad73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-ship prevents broken application code from reaching commit history by running the project’s quality gates in a strict order and stopping immediately when a required check fails.

Core Features & Use Cases

  • Sequential quality gates: Runs type-checking, linting, tests, build steps, and regression checks in order so issues are caught early.
  • First-failure halting: Stops on the first required failure and surfaces the exact tool output to speed up debugging.
  • Docs-only shortcut: Detects when only documentation changed and skips unnecessary code validation.
  • Use case: Before committing a feature or bug fix, use this Skill to verify that the code still compiles, tests pass, and the build succeeds.

Quick Start

Use the pre-ship skill before committing application code so it checks the project’s gates and halts on the first failure.

Frequently Asked Questions about pre-ship

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

FAQPage Schema
How do I run sequential quality gates before committing code?▼

To run sequential quality gates before committing code, use this Skill to enforce ordered type-check, lint, unit test, build, and regression validation on staged changes, halting on the first failure with verbatim error reporting.

Does pre-commit type-checking and linting support Python and Go projects?▼

Pre-commit type-checking and linting support Python and Go projects, as well as TypeScript and similar environments, by inspecting cached diffs and applying ordered validation gates before code is committed.

What is the best way to prevent broken application code from reaching commit history?▼

The best way to prevent broken application code from reaching commit history is enforcing sequential pre-push quality gates that stop immediately when a required check fails and surface the exact tool output.

How do I skip unnecessary code validation when only documentation changed?▼

To skip unnecessary code validation when only documentation changed, this Skill automatically detects docs-only staged changes and bypasses type-check, lint, test, and build steps for those commits.

Why does my pre-commit build stop on the first failing test?▼

A pre-commit build stops on the first failing test because this Skill enforces first-failure halting to catch issues early, immediately surfacing the exact tool output to speed up debugging.

How do I catch regression issues in staged source changes before a push?▼

To catch regression issues in staged source changes before a push, this Skill runs ordered regression validation as a final quality gate, ensuring type, lint, unit test, and build checks pass first.