ship

gunderwonder's avatarfrom gunderwonder

Commit and push changes with an auto-generated commit message. Use when the user says "ship it", "commit and push", or wants to save and deploy their changes.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 1, 2026⬇️1downloads
[Developer Tools]

When & Why to Use This Skill

The 'Ship' skill streamlines the Git version control workflow by automating the staging, committing, and pushing of code changes. It leverages AI to analyze code differences and generate professional, context-driven commit messages while enforcing security best practices by detecting sensitive files and preventing unauthorized pushes to protected branches.

Use Cases

  • Rapid Development Cycles: Use the 'ship it' command to instantly stage, commit, and push small fixes or features, maintaining development momentum without manual Git overhead.
  • Standardizing Commit History: Ensure all project commits follow a consistent, high-quality format that focuses on the 'why' behind changes, improving long-term project maintainability.
  • Security Compliance: Automatically prevent the accidental commitment of sensitive information like .env files or API credentials through built-in safety scans during the staging process.
  • Simplified Branch Management: Automate the process of setting upstream origins and pushing to remote branches, reducing the complexity of multi-branch collaboration.
nameship
descriptionCommit and push changes with an auto-generated commit message. Use when the user says "ship it", "commit and push", or wants to save and deploy their changes.

Ship

Commit and push all changes with a well-crafted commit message.

Instructions

  1. Check current state

    • Run git status to see all changes
    • Run git diff to understand what changed
    • Run git log --oneline -5 to see recent commit style

  2. Stage changes

    • Add relevant files with git add
    • NEVER commit sensitive files (.env, credentials.json, secrets/, etc.)
    • Warn the user if sensitive files are detected

  3. Generate commit message

    • Write in English
    • Focus on the "why" rather than the "what"
    • Keep the first line concise (50-72 chars)
    • Use imperative mood ("Add feature" not "Added feature")

  4. Commit with signature Use HEREDOC format for proper formatting:

    git commit -m "$(cat <<'EOF'
Your commit message here

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

  5. Push to remote

    • Run git push
    • If no upstream is set, use git push -u origin <branch>

  6. Report result

    • Show the commit hash
    • Confirm which branch was pushed
    • Confirm push was successful

Safety

  • NEVER force push
  • NEVER push to main/master without explicit user approval
  • NEVER commit files that look like secrets or credentials
  • If there are no changes, inform the user instead of creating an empty commit