ship

Automate end-of-session verification, conventional commits, and progress tracking.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/cbemister/claude-code --skill ship-cbemister
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/cbemister/claude-code/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/cbemister/claude-code --skill ship-cbemister

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-of-session workflow to ensure code quality, clean commits, and progress tracking after a development session.

Core Features & Use Cases

  • Phase 0: Verification: Run comprehensive verification (security checks, best practices, efficiency, and code standards) before committing.
  • Phase 1: Organization: Group changes into logical, conventional commits and prepare a clean history.
  • Phase 2: Tracking: Update changelog and roadmap progress to reflect completed work.
  • Use Case: When finishing a feature, run the ship skill to verify quality, generate a clean set of commits, and record progress in the project roadmap.

Quick Start

Invoke the ship skill at the end of a development session with /ship to verify work, organize commits, and track progress. Example: after implementing a feature, run /ship in your project context to produce a changelog draft and progress entries.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate end-of-session code verification and commit management?

End-of-session code verification and commit management is automated by running a single command to enforce security checks, run tests, and group changes into conventional commits. This ensures code quality and generates a changelog draft.

What is the best way to organize commits into conventional formats before finishing a feature?

Organizing commits into conventional formats is handled by grouping uncommitted changes into logical sets during your session. This process prepares a clean history and ensures code standards are met before finalizing progress updates.

How do I generate a changelog draft and track progress after a development session?

Generating a changelog draft and tracking progress is achieved by invoking an automated workflow at the end of your session. It records completed work into a project roadmap and outputs a structured changelog draft.

Does this end-of-session workflow run security and best practice checks before committing?

Yes, comprehensive security and best practice checks are enforced before committing. The workflow runs verification checks for code standards, efficiency, and security, guiding you through fixing any blocking issues before commits are created.

Can I use automated progress tracking across multiple software engineering projects?

Automated progress tracking applies across projects to ensure consistent code quality and clean commits after development sessions. It updates roadmap progress and changelog records regardless of the specific project context.

What happens if blocking issues are found during pre-commit verification?

When blocking issues are found during pre-commit verification, the workflow guides you through fixing them. It enforces comprehensive checks and ensures all tests pass before proceeding to commit organization and progress tracking.