Push commits
SkillDev toolsReview and safely push local commits from the current Git branch to its upstream. Use when the user explicitly asks Codex to push commits or invokes $push; require confirmation after showing exactly what will be pushed.
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 commits skill
What this skill tells your AI
The instructions your AI receives, as published by byline-cms/bylinecms.dev in .agents/skills/push/SKILL.md and read by ahel’s review.
Push the current branch without rewriting remote history.
Workflow
- Inspect
git status --short --branch. - If tracked, staged, or untracked changes remain, show them and ask whether pushing the existing commits is still intended. Do not include those changes automatically.
- Determine the current branch and its upstream.
- If an upstream exists, show commits with
git log @{u}..HEAD --oneline. - If no upstream exists, propose
git push -u origin <branch>and show the local commits that would be introduced remotely.
- If an upstream exists, show commits with
- If there are no commits to push, report that and stop.
- Show the branch, remote destination, and complete outgoing commit list. Wait for explicit confirmation.
- Run a normal
git push, or the approvedgit push -u origin <branch>form. Never force-push. - Report the pushed commit range and remote branch, or surface any failure verbatim.
Signals
- GitHub stars
- 34
- Forks
- 2
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
push-byline-cms- Source
- github.com/byline-cms/bylinecms.dev