# Git Push

> Validate and push the intended branch while preserving unrelated work. Use when the user types /git-push.

- Skill: `blockmatic/git-push` (Agent Skill)
- Install (CLI): `npx skillmds@latest add blockmatic/git-push`
- Raw SKILL.md: https://api.skillmd.com/api/skills/blockmatic/git-push/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: blockmatic (https://skillmd.com/u/blockmatic)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/blockmatic/git-push

---


## Purpose and inputs

Invocation requests pushing the current task. Inspect branch, upstream, staged/unstaged changes, and repository Git rules. Do not infer that unrelated working-tree edits belong in the push.

## Steps

1. Review the intended diff and required check results. Remove only temporary debug code introduced by the task.
2. If task changes need committing, follow [git-commit](../git-commit/SKILL.md). Preserve unrelated staged and untracked files.
3. Push to the inspected upstream. If none exists, use the repository's intended remote and current branch; resolve ambiguity before publishing.
4. For a rejected push, inspect divergence and use the repository's non-destructive synchronization workflow. Never force-push or bypass hooks.

## Verification and handoff

- [ ] Required checks and commit hooks passed.
- [ ] The intended branch was accepted by the remote.
- [ ] Unrelated local changes remain intact.

Report branch and push result. Do not create a PR, deploy, or start watching CI unless requested.