skills.rest
jeremy-newhouse
jeremy-newhouseCOMMUNITY
Explore all skills by this author →
GitHub

wa:dev-push

Push the current Git branch after inspecting remotes and divergence.

Updated Mar 26, 2026
Search Tags:#git#push#e2e testing#force-with-lease#divergence#upstream tracking
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-push
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wa:dev-push
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/dev-push
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill prevents common Git push mistakes by checking remotes, assessing divergence, and guiding safe push strategies with clear guardrails.

Core Features & Use Cases

  • Remote and branch safety checks: Verifies at least one remote exists and inspects upstream tracking and ahead/behind divergence.
  • First-push, normal, and diverged workflows: Handles the cases where no upstream is set, where the branch is in sync, and where the branch has diverged.
  • Protected-branch protection: Blocks pushes to main/dev unless the user explicitly confirms.

Quick Start

Run wa:dev-push to push your current branch to origin with upstream tracking after performing the safety checks.

Frequently Asked Questions about wa:dev-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely push a git branch with upstream tracking and divergence checks?▼

Safely pushing a git branch requires verifying remotes with git remote -v, inspecting upstream tracking and ahead/behind divergence via git status, and then applying the appropriate push strategy based on your specific workflow scenario.

What's the best way to handle a diverged git branch when pushing to remote?▼

Handling a diverged git branch involves inspecting the ahead/behind status to determine divergence, then applying optional force-with-lease handling to safely push your local commits to the remote repository without overwriting unexpected changes.

How do I set up upstream tracking for a first git push to a new remote branch?▼

Setting up upstream tracking for a first git push requires confirming at least one remote exists, verifying branch safety, and executing git push with the appropriate strategy to configure remote tracking for your current branch.

Can I push commits to main or dev branches safely without overwriting remote changes?▼

Pushing commits to main or dev branches is blocked by protected-branch protection unless you explicitly confirm, preventing unsafe pushes to critical branches and ensuring remote changes are not accidentally overwritten.

When should I use force-with-lease instead of a normal git push?▼

Use force-with-lease instead of a normal git push when your branch has diverged from the remote, allowing you to safely update the remote branch while ensuring you do not overwrite unexpected upstream commits.

Related Skills

Explore More Software Engineering Skills→
saadjssaadjs

git-incremental-commits

Convert uncommitted changes into small conventional commits via git add -p.

Community
Advanced
cajiascajias

gh-pr-create-must-push-error

Create GitHub pull requests with gh pr create using explicit --head branch flags.

Community
Basic
gonzalezpazmonicagonzalezpazmonica
47

savia-hub-sync

Synchronize SaviaHub repositories between local and remote instances with Git.

Community
Advanced
jcdendritejcdendrite
4

git-feature-branch-sync

Synchronize a divergent Git feature branch with the remote default branch.

Community
Advanced