Git Push

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

blockmatic 43d1124 1.1 KB Updated

File contents

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. 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.

blockmatic/basilic-skills/tree/main/skills/workflow/git-push commit 43d1124e0b

Frequently asked questions

npx skillmds@latest add blockmatic/git-push