Run any Skill in Manus with one click

zoo-push

Stars5

Forks1

UpdatedJuly 8, 2026 at 16:49

Manually publish completed changes by reading repo push instructions, running Zoo Rebase first, and pushing or following repo PR/trunk workflow only when rebase says safe. Use only when explicitly asked to push, publish, open PR, or run Zoo Push.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

andreyvit

andreyvit/zoo

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	zoo-push
description	Manually publish completed changes by reading repo push instructions, running Zoo Rebase first, and pushing or following repo PR/trunk workflow only when rebase says safe. Use only when explicitly asked to push, publish, open PR, or run Zoo Push.

Follow .zoo/zoo.md, .zoo/push.md if exists.

Only when user explicitly asks to push/publish.

Run zoo-rebase inline. Bail and follow zoo-rebase routing if outcome is Unsafe; continue if OK.
Push.
If remote moved, repeat zoo-rebase and retry until published or unsafe.
Report command, remote branch, PR URL if applicable, final git status, result - Pushed / Opened PR / Unsafe to push / Failed.

Do not block push merely because conflicts happened; resolved conflicts + passing validation is safe.
Do not push unresolved conflicts, failed validation, or uncommitted trackable changes outside ignored task roots.
Do not alter unrelated dirty work.

More from this repository

same repository

linus

andreyvit/zoo

Rant, swear, and insult like Linus Torvalds on the LKML — brutally blunt technical criticism. Use when user asks for Linus review/voice or for swearing.

2026-07-085

terse

andreyvit/zoo

Terse writing/comm style. Use for agent messages, skills, instructions, memories, docs, comments, commit messages and similar.

2026-07-085

zoo-add

andreyvit/zoo

Record user feedback for the active task without interrupting work. Use only when explicitly asked to add, remember, or handle later.

2026-07-085

zoo-browser-verification

andreyvit/zoo

Verify browser-visible behavior and capture focused UI evidence. Use after implementation for browser-impact work or when explicitly requested.

2026-07-085

zoo-cleanup-finished-specs

andreyvit/zoo

Archive completed Zoo spec files and resolved proposal files. Use when cleaning finished `.spec` work, moving completed specs into `archived/`, or moving implemented/rejected proposals into archive while honoring repo-local Zoo path overrides.

2026-07-085

zoo-code-review

andreyvit/zoo

Tiered code review gate: tests, scripted checks, narrow parallel checks, broad review. Invokable standalone on any diff or inside Zoo workflow.

2026-07-085

name	zoo-push
description	Manually publish completed changes by reading repo push instructions, running Zoo Rebase first, and pushing or following repo PR/trunk workflow only when rebase says safe. Use only when explicitly asked to push, publish, open PR, or run Zoo Push.

Follow .zoo/zoo.md, .zoo/push.md if exists.

Only when user explicitly asks to push/publish.

Run zoo-rebase inline. Bail and follow zoo-rebase routing if outcome is Unsafe; continue if OK.
Push.
If remote moved, repeat zoo-rebase and retry until published or unsafe.
Report command, remote branch, PR URL if applicable, final git status, result - Pushed / Opened PR / Unsafe to push / Failed.

Do not block push merely because conflicts happened; resolved conflicts + passing validation is safe.
Do not push unresolved conflicts, failed validation, or uncommitted trackable changes outside ignored task roots.
Do not alter unrelated dirty work.