push
/push
Use for /push, or 'push my branch' — pushes the current branch to origin, setting upstream on first push, before opening a PR with /pr.
- Author
- egregore-labs ↗
- Repository
- egregore ↗
- Licence
- MIT
- Last repository change
- 16.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use for /push, or 'push my branch' — pushes the current branch to origin, setting upstream on first push, before opening a PR with /pr.
Triggers from the description
Original author description
Use for /push, or 'push my branch' — pushes the current branch to origin, setting upstream on first push, before opening a PR with /pr.
How it works
- When to invoke
- Execution boundary
- Before anything else
- What to do
- Example
- Next
SKILL.md preview
---
name: push
description: "Use for /push, or 'push my branch' — pushes the current branch to origin, setting upstream on first push, before opening a PR with /pr."
---
Push current branch to remote.
## When to invoke
User says: "/push", "push my branch", "push this up", "get my branch onto GitHub", or needs the current branch pushed to origin before opening a PR.
Not this: ready to open the PR itself → `/pr` (run after push).
## Execution boundary
This is a deterministic Git transport operation. Run it inline; do not spend a
Loom/model-routing call or delegate it to another agent.
## Before anything else
Resolve the base with `bash bin/base-branch.sh` (add the managed repo name when
applicable); it prints `{base}` or fails, in which case stop.
Check `git branch --show-current`. If on a protected branch (`{base}`, `develop`,
`main`, or `master`):
→ Use the resolved base branch (default `"develop"`)
→ Create a working branch: `git fetch origin "{base}" --quiet`, then
`git checkout --no-track -b dev/{author}/{topic-slug} "origin/{base}"`
→ Tell the user: "Creating a working branch for this..." — never mention git commands to the user.
→ Then proceed with the push.
## What to do
1. Push current branch to origin
2. Set upstream if first push
## Example
```
> /push
Pushing feature/2026-01-20-mcp-authentication...
git push -u origin feature/2026-01-20-mcp-authentication
✓ Pushed
Branch is now on GitHub.
Run /pr when ready for review.
```
## Next
Run `/pr` when ready for review.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · egregore-labs/egregore | 95 | MIT |
| AsiaOstrich/universal-dev-standards | 100 | MIT |
| hamedmp/matrix-os | 100 | AGPL-3.0 |
| AsiaOstrich/universal-dev-standards | 100 | MIT |
| AsiaOstrich/universal-dev-standards | 100 | MIT |
| JQ-WCoding/devkit | 100 | MIT |
| Mooshieblob1/MooshieUI | 100 | AGPL-3.0 |
| AsiaOstrich/universal-dev-standards | 100 | MIT |
| tibursocampos/agent-dev-toolkit | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2e53d9b81e40 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95update-branch
Use only when the user explicitly asks to update the current local feature branch from origin's default branch. Merge in place in a clean ordinary checkout; no branch switching, rebase, push, or feature-upstream sync. - 100push-to-forked-pr
Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is usually the upstream). Invoke when the user says things like "push straight to PR #N", "push to the forked PR", "update… - 100commit-push
Commit changes and push to the current branch remote. Use when you want to commit local changes and push them upstream in one workflow, with branch protection against main/master. - 90commit-push-current
Use when a human asks to commit and push, not publish, the checked-out branch, including directly to the default branch, with no branch creation and no pull request. Not for a feature branch off the default: use commit-push-pr in its no-PR mode. - 100publish-branch
Use when a human asks to publish, not commit and push, the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch. - 100force-push-downstream
Force-push a branch and all its downstream branches to origin. Auto-detects the downstream tree and skips branches already up-to-date. Triggers on: force push downstream, push chain, push all branches.