ship-feature

Run verification, typechecking, linting, and update task and milestone statuses.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ozkangu/agent-mesh --skill ship-feature-ozkangu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-feature
Source: https://github.com/ozkangu/agent-mesh/tree/main/commands/ship-feature
Command: npx skills add https://github.com/ozkangu/agent-mesh --skill ship-feature-ozkangu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines feature delivery by orchestrating verification, testing, linting, and status updates so engineers ship reliable code with reduced manual steps.

Core Features & Use Cases

  • End-to-end feature shipping: run verification, fix failures, run typechecks, lint, commit changes, and update task and milestone progress.
  • Automation of repository tasks: read current context, update data files, and regenerate the AI context for consistent prompts.
  • Use Case: When a feature is ready, trigger this workflow to ensure all checks pass and the project board reflects progress.

Quick Start

Run the ship-feature sequence to verify, test, commit, and update task status.

Frequently Asked Questions about ship-feature

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

FAQPage Schema
How do I automate feature shipping with linting and typechecking?

Automating feature shipping requires orchestrating verification, typechecking, and linting to ensure reliable code delivery with reduced manual steps. This workflow runs checks, commits changes, and updates task progress automatically.

What is the best way to update task and milestone statuses after committing code?

Updating task and milestone statuses after a commit is handled by reading repository context and updating data files to reflect progress. This ensures the project board stays synchronized with the latest validated feature delivery.

Do I need pnpm to run verification and typechecks for feature shipping?

Yes, you need pnpm installed locally to run verification, typechecks, and linting. The workflow requires local tooling and access to repository data to execute tests and regenerate the AI context.

How does regenerating AI context work during feature delivery?

Regenerating AI context works by reading current repository data and updating data files to maintain consistent prompts. This automation step ensures the project context accurately reflects the newly committed and validated features.

Can I fix verification failures automatically before committing a feature?

Yes, the feature shipping workflow attempts to fix verification failures automatically. It runs checks, addresses failures, executes typechecks and linting, and then proceeds to commit changes only after all validations pass.

What are the limitations of automating repository tasks for feature shipping?

Limitations include a strict dependency on local pnpm tooling and direct access to repository data to read context. Without these environment prerequisites, the workflow cannot run tests or regenerate the required AI context.