push
SkillFiles & storageCommit already-staged changes and push to remote. Never stage new files. Use when changes are already staged or the user explicitly says push staged changes.
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 push skill
What this skill tells your AI
The instructions your AI receives, as published by vvedantb/eva in .agents/skills/push/SKILL.md and read by ahel’s review.
Commit ONLY already-staged changes and push to the remote.
CRITICAL: Do NOT run git add, git add -A, git add ., or stage any files. Only commit what is already in the staging area.
Steps:
- Run
git diff --cached --statto review what's staged - If nothing is staged, stop and tell the user — do NOT stage files yourself
- Run
git log --oneline -5to see recent commit message style - Write a commit message following the repo's convention (lowercase prefix like
feat:,fix:,refactor:, etc.) — short title summarizing the WHY, not the WHAT - Commit using a HEREDOC for the message (do NOT use
git addbefore committing) - Push to the remote with
git push - Print the resulting commit hash
Signals
- GitHub stars
- 101
- Forks
- 7
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
push-vvedantb- Source
- github.com/vvedantb/eva