Enforce pre-push checks for commit hygiene and force-push safety.
npx skills add https://github.com/deandum/claude-resources --skill ops-git-remote
Please help me install this Agent Skill. Skill: ops/git-remote Source: https://github.com/deandum/claude-resources/tree/main/skills/ops/git-remote Command: npx skills add https://github.com/deandum/claude-resources --skill ops-git-remote
Remote git pushes can cause irreversible changes or disrupt collaboration if done without guardrails. This skill enforces a disciplined push protocol, including validating commits, setting upstream tracking, and governing force-push and tag publication to protect workflows.
Review your local branch, ensure commits are clean, and push to origin only after confirming upstream tracking and safety rules.
High-intent search queries and answers about installing and using this skill.
Safe git pushes require pre-push checks for commit hygiene and base-branch alignment. You enforce upstream discipline by validating commits, setting explicit upstream tracking, and using --force-with-lease to prevent overwriting remote changes.
Force-with-lease is a git push safeguard that prevents overwriting commits when updating remote branches. Use it instead of standard force-push to protect collaborative workflows, ensuring you only overwrite remote branches if your local refs match the remote state.
Setting upstream tracking requires explicit configuration during your initial git push. You establish the remote branch relationship by validating commit hygiene first, then pushing with correct base-branch alignment to prevent accidental exposure of incomplete work.
Yes, the git push workflow governs tag publication in collaborative projects with protected branches. It manages tag updates alongside branch management, ensuring pre-push checks validate commit hygiene and base-branch alignment before any tag publication occurs.
Force-push safeguards using --force-with-lease limit protection to local ref verification and do not prevent conflicts when remote branches diverge significantly. You should avoid standard force-push entirely on protected branches to maintain collaborative workflow integrity.
leolionartCommit changes, push to the remote branch, and draft release notes.
drnDeploy the latest master branch to production with a version tag.
yt8766Stage, commit, validate hooks, and push Git changes to origin.
ekozmdevAutomates Git pre-push checks displaying branch, status, and upstream information via Bash script.
