ship — community EZVals, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing streamlined testing and version management on the dev branch. Ship dev to main. Creates a release with version bump, changelog, and tag.

camronh camronh
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
36
Canonical Locale
en
Detected Body Locale
en

Perfect for Development Agents needing streamlined testing and version management on the dev branch. Ship dev to main. Creates a release with version bump, changelog, and tag.

Core Value

Empowers agents to automate testing and versioning using a code-first eval framework, facilitating parallel testing with `-n auto` and changelog updates in `docs/changelog.mdx`.

Ideal Agent Persona

Perfect for Development Agents needing streamlined testing and version management on the dev branch.

↓ Capabilities Granted for ship

Automating test runs on the dev branch
Generating version bumps based on changelog updates
Debugging test failures with parallel testing

! Prerequisites & Limits

  • Requires being on the `dev` branch
  • Needs access to `docs/changelog.mdx` for versioning

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is ship?

Perfect for Development Agents needing streamlined testing and version management on the dev branch. Ship dev to main. Creates a release with version bump, changelog, and tag.

How do I install ship?

Run the command: npx killer-skills add camronh/EZVals/ship. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for ship?

Key use cases include: Automating test runs on the dev branch, Generating version bumps based on changelog updates, Debugging test failures with parallel testing.

Which IDEs are compatible with ship?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for ship?

Requires being on the `dev` branch. Needs access to `docs/changelog.mdx` for versioning.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add camronh/EZVals/ship. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use ship immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

ship

Install ship, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Follow these steps in order:

1. Confirm on Dev

  • Verify we're on the dev branch
  • If not, stop and ask

2. Run Tests

  • Run tests and ensure all tests pass. (Use -n auto to run tests in parallel)
  • If tests fail, STOP and report the failures

3. Version Bump

  • Read docs/changelog.mdx to see what's in the ## Unreleased section
  • Suggest the next version (based on existing versions in the changelog)
  • Update docs/changelog.mdx: change ## Unreleased to ## <version> - <today's date>
  • Update pyproject.toml version to match
  • Run uv lock to sync the lock file with the new version
  • Summarize the changes for this version in a human friendly way. Focus on impactful changes and user facing changes.

4. Update Skill Version

  • Update the version comment in ezvals/skills/evals/SKILL.md (the <!-- Version: X.X.X --> line) to match the release version
  • The skill version MUST match the release tag — the Sync Skill to Marketplace workflow will fail otherwise

5. Commit & Push Dev

bash
1git add -A
2git commit -m "release <version>"
3git push origin dev

6. Merge to Main

bash
1git checkout main
2git pull origin main
3git merge dev
4git push origin main

7. Tag & Push

bash
1git tag v<version>
2git push origin v<version>

8. Return to Dev

bash
1git checkout dev

PyPI Publishing (Automatic)

Publishing to PyPI is handled automatically by GitHub Actions:

  • Dev builds (.github/workflows/publish-dev.yml): Every push to main publishes a dev version (0.0.0.dev{timestamp}) to PyPI
  • Release builds (.github/workflows/publish.yml): Pushing a tag like v0.1.0 triggers a release publish to PyPI

You don't need to manually run uv publish - just push the tag and the workflow handles it.

Error Handling

  • If tests fail → stop and report
  • If merge conflicts occur → stop and ask for help
  • If not on dev → stop and ask

Related Skills

Looking for an alternative to ship or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer