ship

Classify engineering request intent and route to the matching production workflow.

121|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill ship-agentsystemlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/ship
Command: npx skills add https://github.com/AgentSystemLabs/core --skill ship-agentsystemlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the friction of picking the right engineering workflow by automatically classifying your intent and dispatching the correct core skill to deliver code-ready results without committing or publishing changes.

Core Features & Use Cases

  • Intent classification: Detects CREATE, EVOLVE, POLISH, REMOVE, FIX, or AUDIT requests and routes to the corresponding workflow.
  • Risk-aware depth selection: Chooses fast, balanced, or production depth based on risk and complexity signals, with user overrides where applicable.
  • Pipeline transparency and stop-before-git: Announces the plan, runs the routed workflow, and reports findings before you publish via /commit, /commit-and-push, or /open-pr.
  • Use case: Turn a high-level directive like "ship production-ready billing improvements" into the correct sequence of feature/code, verification, and audit steps appropriate to the change type.

Quick Start

Use the ship skill by telling the agent what you want to achieve, such as: ship production-ready authentication and billing fixes for my current app.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate workflow routing for production-ready code delivery?

Automated workflow routing classifies your engineering intent and dispatches the correct core skill to prepare production-ready changes. It selects an execution depth matching risk and complexity before you publish via git commands.

What is the best way to assess risk and complexity before committing code changes?

Risk assessment evaluates your engineering request to select a fast, balanced, or production execution depth. This ensures your code delivery workflow matches the complexity of creating, fixing, or evolving features.

How do I set up git publish gating for automated engineering workflows?

Git publish gating requires explicit pipeline announcement and confirmation before any version control actions occur. The workflow stops before git operations, reporting findings so you can manually run /commit, /commit-and-push, or /open-pr.

Can I use intent classification to route changes across different engineering scenarios?

Intent classification detects CREATE, EVOLVE, POLISH, REMOVE, FIX, and AUDIT scenarios. It routes each request into the corresponding production workflow, invoking the appropriate core skill with mode and include or skip overrides.

Does automated engineering mode selection work for high-level software directives?

Engineering mode selection processes high-level directives by classifying intent and choosing an appropriate execution depth. It transforms broad requests into the correct sequence of feature, code, verification, and audit steps.

Why should I use automated routing instead of manually picking an engineering workflow?

Automated routing eliminates the friction of manual workflow selection by evaluating risk and delegating to the correct core skill. It enforces production gating and transparency without reimplementing the underlying pipeline.