push

Push local commits to a remote Git repository with safety checks.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bswrundquist/devtools --skill push-bswrundquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/push
Command: npx skills add https://github.com/bswrundquist/devtools --skill push-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users push their local code commits to a remote repository safely, preventing accidental data loss or conflicts.

Core Features & Use Cases

  • Safe Pushing: Ensures commits are pushed without overwriting or causing divergence.
  • Branch Verification: Confirms the correct branch and remote are targeted.
  • Conflict Prevention: Warns against force pushing to main/master and suggests safe alternatives like git pull --rebase when divergence occurs.
  • Use Case: After completing a feature and reviewing your local changes, use this skill to push your work to the shared repository without risking conflicts with ongoing team efforts.

Quick Start

Use the push skill to push your current branch to the remote repository.

Frequently Asked Questions about push

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

FAQPage Schema
How do I safely push local commits to a remote Git repository?

Safely pushing commits to a remote Git repository requires verifying your branch status and confirming the correct remote target before execution. This prevents accidental data loss and avoids overwriting remote changes.

What happens if my local branch has diverged from the remote repository?

If your local branch has diverged from the remote repository, you will be guided through divergence resolution using `git pull --rebase`. This ensures your local commits are safely integrated before pushing.

Can I force push commits to the main or master branch?

No, you cannot force push commits to main or master branches. The process includes safety checks that warn against force pushing to main branches and suggests safe alternatives to prevent accidental data loss.

Why do I need to verify my branch before pushing code?

Verifying your branch before pushing code confirms the correct branch and remote are targeted. This branch verification step ensures commits are pushed without causing divergence or overwriting ongoing team efforts.

How do I prevent conflicts when pushing commits to a shared repository?

To prevent conflicts when pushing commits to a shared repository, the process manages branch status verification and uses `git pull --rebase` for divergence resolution. This ensures safe code deployment without risking team efforts.