ship

Execute quality checks, update documentation, and perform conventional commits and pushes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of preparing your code for commit and push, ensuring quality and consistency.

Core Features & Use Cases

  • Automated Quality Checks: Runs linters, type checkers, tests, and builds to ensure code integrity.
  • Documentation Updates: Guides you through updating essential project documentation like READMEs, changelogs, and design docs.
  • Version Bumping: Helps manage service worker cache versions for PWA updates.
  • Conventional Commits: Enforces a standardized commit message format for better project history.
  • Use Case: After a productive coding session, you can invoke this Skill to automatically run all checks, update relevant documentation files, and prepare a well-formatted commit and push.

Quick Start

Run the ship skill to perform end-of-session checks, commit, and push.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my end-of-session git commit and push workflow?

Automating your end-of-session git workflow involves running sequential quality checks, updating documentation, and generating conventional commit messages before pushing. This ensures code integrity and project consistency through deterministic steps without manual intervention.

What is the best way to enforce code quality checks before a git push?

The best way to enforce code quality before pushing is to automate linters, type checkers, tests, and builds sequentially. This deterministic process catches errors and verifies integrity before generating a conventional commit.

How do I automate conventional commits and documentation updates together?

You can automate conventional commits and documentation updates by running a workflow that sequentially updates READMEs and changelogs, bumps cache versions, and then formats the final commit message to standardize project history.

Does automated end-of-session workflow support PWA service worker cache versioning?

Automated end-of-session workflows can manage service worker cache versions for PWA updates. This is handled during the documentation and version management phase to ensure users receive the latest application updates.

Can I run linters and type checkers automatically before committing code?

Yes, automated quality checks can run linters and type checkers before committing code. These checks execute as part of a sequential workflow to verify code integrity and enforce project consistency prior to the push.

What are the limitations of automating documentation updates during a commit?

Automating documentation updates during a commit guides you through updating essential files like READMEs and changelogs rather than fully autonomous generation. The workflow enforces consistency but requires sequential, deterministic steps to complete.