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
- 1
- 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.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
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
SKILL.md has no level-two headings · 26 lines, 162 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.' --- <!-- generated-by: bin/codex-sync-skills.sh --> # Egregore push Adapter This adapter runs the canonical Egregore workflow for `push`. Its one maintained body is `.claude/skills/push/SKILL.md`; read that file completely and follow it here. Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an `Other:` option and wait for the user. 1. Read `.claude/skills/push/SKILL.md` for the workflow details. 2. Run the referenced `bin/` scripts directly from Codex. 3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required. 4. For every external notification, follow `.claude/context/notification-consent.md`: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval. 5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when `egregore.json` declares `"mode": "local"`. 6. Never call the deprecated `egregore-handoff` CLI for Egregore project handoffs.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · egregore-labs/egregore | 86 | 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 0cef49e8a974 (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… - 100update-origin
Updates the current branch from an origin branch via standard merge, with a recoverable backup and safe conflict resolution. Use when the user runs /update-origin or asks to update, sync, or merge their branch with main (or another origin branch). - 100pr
Use when the user runs /pr to commit the current work, push the branch, and open or update its pull request. - 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.