Use for /push, or 'push my branch' — pushes the current branch to origin, setting upstream on first push, before opening a PR with /pr.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Push current branch to remote.
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).
This is a deterministic Git transport operation. Run it inline; do not spend a Loom/model-routing call or delegate it to another agent.
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.
> /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.
Run /pr when ready for review.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
The English summary is being prepared. Showing the original description.
Draft, preview, and explicitly send an Egregore group announcement. Use for /announce, telling the team something, or notifying everyone—not a direct message or structured handoff.
The English summary is being prepared. Showing the original description.
Capture an effective prompting or steering technique as a reusable canonical pattern. Use when a prompt chain worked especially well; use /reflect for insight about the work and /note for a private thought.
The English summary is being prepared. Showing the original description.
Create a working branch from what you are about to work on. Use for /branch, or any request to start a new branch before making changes.
The English summary is being prepared. Showing the original description.
Run diagnostics on an Egregore environment and render a health report, repairing safe local Runtime problems when possible. Use for /checkup, a health check, or when something is broken and the root cause is unclear.
The English summary is being prepared. Showing the original description.
Stage changes and create a commit with a properly formatted message. Use for /commit, or saving work locally — not sharing it (/push) or opening a pull request (/pr).
The English summary is being prepared. Showing the original description.