One-click install
npx skills add https://github.com/tcytan/tecton --skill ship-tcytan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/tcytan/tecton/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/tcytan/tecton --skill ship-tcytan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or unsafe releases by enforcing a structured, multi-phase checklist that validates code, reviews risk with AI, bumps versions, updates changelogs, and publishes artifacts with traceable outputs.

Core Features & Use Cases

  • Phase-gated release pipeline: Runs pre-flight checks, AI code review, version bump, changelog/commit, optional PR creation, optional platform publish, and a terminal GitHub release gate.
  • Multi-project version handling: Detects and updates versions for npm (package.json), Python (pyproject.toml), and generic VERSION files, including package-lock updates when relevant.
  • AI-powered risk assessment: Uses CCW CLI to analyze diffs and block the release on critical issues while allowing warnings to proceed as DONE_WITH_CONCERNS.
  • Registry-aware publishing with safety skips: Publishes to npm/PyPI/crates.io when applicable, verifies the new version is live, and skips publish for private packages.
  • Audit-ready structured outputs: Each phase emits structured JSON suitable for traceability and downstream automation.

Quick Start

Tell your agent to run the ship Skill to release by triggering it with the command: ship.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate GitHub releases and npm publishing with quality gates?

Automated release pipelines enforce pre-flight checks, AI code review, version bumping, and changelog generation before publishing to npm or creating a tagged GitHub release. This multi-phase process ensures code quality gates are passed before any registry artifact goes live.

What is the best way to generate changelogs and bump versions for Python PyPI packages?

Generating changelogs and bumping versions for PyPI packages involves detecting pyproject.toml, updating the version file, creating a commit, and publishing to the registry. The release pipeline automates this sequence while verifying the new version is live before completion.

How does AI code review work in a continuous integration release pipeline?

AI code review in a release pipeline uses CCW CLI to analyze merge-base diffs and assess risk. It blocks releases on critical issues while allowing warnings to proceed as DONE_WITH_CONCERNS, ensuring unsafe changes are caught before version bumping or publishing.

Does automated version bumping support Rust crates.io and generic VERSION files?

Automated version bumping supports Rust projects by publishing to crates.io, and handles generic VERSION files for non-standard projects. It detects the appropriate version file, applies the bump, and updates package-lock files when relevant for JavaScript or TypeScript.

Can I skip registry publishing for private packages during an automated release?

Registry-aware publishing includes safety skips for private packages, preventing accidental exposure. The pipeline only publishes to npm, PyPI, or crates.io when applicable, and skips the publish phase entirely for private modules.

Why use phase-gated execution for GitHub release and registry artifact publishing?

Phase-gated execution prevents broken releases by enforcing sequential checks from working branch to published artifact. Each phase emits structured JSON outputs for audit traceability, ensuring downstream automation can verify that version detection, AI review, and publishing completed successfully.