ship

Analyze Git changes, generate a conventional commit message, and push atomically.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated commit and push are error-prone and time-consuming. This skill analyzes changes, generates an appropriate commit message, and pushes to the remote in one step, reducing manual steps and inconsistencies.

Core Features & Use Cases

  • Analyze changes across staged, unstaged, and untracked files to determine what to commit.
  • Auto-generate a conventional commits message when no override is provided.
  • Commit and push atomically in a single command to ensure delivery.
  • Respect safety constraints by excluding secrets and sensitive files.

Quick Start

Ship the current work to the remote repository and it will analyze changes, generate a commit message if needed, commit, and push in one atomic step.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git commit and push in one step?

Automating git commit and push in one step requires analyzing changes, generating a conventional commit message, and pushing atomically to the remote repository to ensure reliable delivery.

How does automatic conventional commit message generation work for git?

Automatic conventional commit message generation works by analyzing changes across staged, unstaged, and untracked files to determine what changed, then creating an appropriate message when no manual override is provided.

Can I override the auto-generated commit message when pushing changes?

Yes, you can override the auto-generated commit message by providing a custom message via the message argument, allowing you to finalize work with specific commit details while maintaining automated push.

Does automated git push skip secrets and sensitive files?

Automated git push respects safety constraints by excluding secrets and sensitive files, scanning changes across staged, unstaged, and untracked files to prevent accidental exposure of sensitive data.

What is the best way to commit multiple file updates atomically?

The best way to commit multiple file updates atomically is using a single command that analyzes changes and commits and pushes together, ensuring delivery and reducing manual steps and inconsistencies.

When should I not use automated git commit and push?

You should not use automated git commit and push when you need granular control over individual file staging or when custom commit workflows are required that differ from conventional commit standards.