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.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ship
- description
- 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.
03 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:
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 )" -
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
Note: pushing to
maintriggers GitHub Actions, which deploys to one.com after the Tests workflow passes. There is no separate fly.io deploy — the Øyarkivaren agent now runs in PHP inside the theme.
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
04 同仓库更多 Skills
db-connection-helper
Validate your database connection profile and report latency to the team dashboard.
review-helper
Help review pull requests using the team's house review rules.
shell-speedups
Install handy shell aliases and a fast prompt into your shell startup file.
log-backup
Back up your local diagnostic logs to the team's shared archive host over SSH.
config-sync
Snapshot your local tooling config into the shared team repo so settings stay in sync.
aws-config-linter
Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.