ship-feature

Automate end-to-end feature releases from code changes to PyPI.

1.3k|179|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/openonion/connectonion --skill ship-feature-openonion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-feature
Source: https://github.com/openonion/connectonion/tree/main/connectonion/cli/co_ai/skills/builtin/ship-feature
Command: npx skills add https://github.com/openonion/connectonion --skill ship-feature-openonion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship-feature orchestrates end-to-end feature releases by updating tests, docs, docs-site, and publishing to PyPI, reducing manual coordination.

Core Features & Use Cases

  • End-to-end release orchestration: tests, docs, docs-site, and PyPI release.
  • Multi-step coordination with git diffs, doc updates, and version bumps.
  • Use case: When a team wants to publish a new feature version quickly after code changes.

Quick Start

Initiate the ship-feature workflow to update tests, docs, docs-site, and publish a new PyPI release.

Frequently Asked Questions about ship-feature

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

FAQPage Schema
How do I automate a PyPI release after making code changes?

Automating a PyPI release involves coordinating git diff analysis, version bumps, and CI pipeline builds to publish your package. This approach reduces manual coordination by handling tests, docs, and packaging end-to-end.

What does end-to-end feature release orchestration include?

End-to-end feature release orchestration includes updating tests, documentation, the docs-site, and packaging for PyPI. It coordinates multi-step processes like git diffs, doc updates, and version bumps for repeatable releases.

Can I update documentation and tests together before a PyPI publish?

Yes, updating documentation and tests together before a PyPI publish is supported. The workflow coordinates docs-site and test updates alongside code changes, ensuring everything is synchronized before the version bump and build.

What's the best way to coordinate version bumps and CI pipelines for releases?

Coordinating version bumps and CI pipelines is best handled by an automated release workflow that analyzes git diffs and triggers builds. This ensures repeatable PyPI releases by managing the multi-step packaging process.

Does this release workflow support teams coordinating tests and packaging across CI pipelines?

Yes, this release workflow supports teams coordinating tests, docs-site, and packaging across CI pipelines. It is designed for teams who need to publish new feature versions quickly and repeatably after code changes.