ship

Stage all Git changes, generate a commit message, and push to the current branch.

114|29|Updated Nov 23, 2019

Search Tags:#git #workflow #commit #push #ship #version-control

Ready to run

npx skills add https://github.com/helderberto/dotfiles --skill ship

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/helderberto/dotfiles/tree/main/claude/.claude/skills/ship
Command: npx skills add https://github.com/helderberto/dotfiles --skill ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of committing and pushing changes in a Git repository.

Core Features & Use Cases

Stage and commit: Automatically stage all changes and generate a commit message from the changed files.
Safe pushing: Push to the current branch without forcing pushes, honoring pre-commit hooks.
Use case: Ideal for daily development cycles where code, docs, or scripts are updated and need to be captured in version history.

Quick Start

Review status and diffs, generate a commit message from the changed files, stage all changes with git add -A, commit, and push to the current branch.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automatically stage, commit, and push changes in a Git repository?▼

To automatically commit and push Git changes, you can automate the workflow by staging all modified files with git add -A, generating a commit message from the changed files, and pushing to the current branch.

Can I automatically generate a commit message from changed files in version control?▼

Yes, you can generate a commit message directly from changed files in version control by reviewing the diffs and automatically crafting a descriptive message to pair with staging all changes.

Does automatic Git pushing run pre-commit hooks and prevent force pushes?▼

Safe automatic Git pushing honors pre-commit hooks and explicitly prevents force pushes, ensuring that repository history is protected and all validation checks run before code is committed.

How do I avoid committing secrets when automating Git workflows?▼

To avoid committing secrets during Git workflow automation, the commit process includes safeguards that detect and block sensitive information before staging changes and pushing to the current branch.

What is the best way to automate daily development cycles for code updates?▼

The best way to automate daily development cycles is using a Git workflow skill that stages all code, doc, or script updates, generates a commit message, and captures them safely in version history.

When should I not use automatic staging with git add -A for commits?▼

You should not use automatic staging with git add -A when you have local untracked files or environment configurations that you do not want included in the version control history and pushed to the remote branch.