Agent skill
ship
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/devops/ship-gunderwonder-bleikoya-2023
SKILL.md
Ship
Commit and push all changes with a well-crafted commit message.
Instructions
-
Check current state
- Run
git statusto see all changes - Run
git diffto understand what changed - Run
git log --oneline -5to see recent commit style
- Run
-
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
- Add relevant files with
-
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")
-
Commit with signature Use HEREDOC format for proper formatting:
bashgit 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 )" -
Push to remote
- Run
git push - If no upstream is set, use
git push -u origin <branch>
- Run
-
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?