ship
SkillFiles & storageStage session-related files, commit with a conventional message, and push to remote. Use when the user asks to ship, commit and push, or finish a session with git.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the ship skill
What this skill tells your AI
The instructions your AI receives, as published by vvedantb/eva in .agents/skills/ship/SKILL.md and read by ahel’s review.
Stage relevant files, commit, and push to remote.
- Run the
/changelogstep first: review this session's changes and, only if they amount to a medium-to-large change or feature (skip quick fixes and bug fixes), add an entry to the top ofinternal/changelog/<YYYY-MM>.md(the current month's file) per the/changelogrules. Stage this edit with the code in step 4. - Run
git status -uandgit log --oneline -5in parallel - Identify session-related files, excluding pre-existing dirty files
- Stage with
git addusing specific paths (nevergit add -Aor.) - Write commit message following repo convention (lowercase prefix: feat/fix/refactor) — summarize WHY, not WHAT
- Commit with HEREDOC, then
git push - Print commit hash and summary
Signals
- GitHub stars
- 101
- Forks
- 7
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
ship-vvedantb- Source
- github.com/vvedantb/eva