Skip to content
Skills Library
Programming · Automation

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.

Repository
egregore ↗
Licence
MIT
Last repository change
16.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.

Licence

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

push my branch
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

  1. When to invoke
  2. Execution boundary
  3. Before anything else
  4. What to do
  5. Example
  6. Next
Original SKILL.md headings · 48 lines, 212 words
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

RepositoryScoreLicence
This page · egregore-labs/egregore95MIT
AsiaOstrich/universal-dev-standards100MIT
hamedmp/matrix-os100AGPL-3.0
AsiaOstrich/universal-dev-standards100MIT
AsiaOstrich/universal-dev-standards100MIT
JQ-WCoding/devkit100MIT
Mooshieblob1/MooshieUI100AGPL-3.0
AsiaOstrich/universal-dev-standards100MIT
tibursocampos/agent-dev-toolkit100MIT

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.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.