skills.rest
TMI-apps
TMI-appsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

push

Validate and push committed Git changes to a remote repository.

2|Updated Dec 22, 2025
Search Tags:#git#workflow#branching#push#pull-request#version-control
One-click install
npx skills add https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor --skill push-tmi-apps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor/tree/main/.cursor/skills/push
Command: npx skills add https://github.com/TMI-apps/boilerplate-vite-supabase-mui-cursor --skill push-tmi-apps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushing unfinished work or unverified commits to a shared repository can risk breaking builds or corrupting history. This Skill defines a safe push workflow that enforces pre-push checks and clear guidance to minimize mistakes.

Core Features & Use Cases

  • Pre-push validation: ensures a clean working tree and at least one commit before pushing.
  • Safety checks: validates branch and remote state and warns against pushing to main without review.
  • Push governance: guides correct branch usage, supports feature branches, and promotes PR-based updates.

Quick Start

Execute the push command after finishing work to publish your local commits 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 commits to a remote Git repository without breaking the build?▼

To push commits safely, you need a workflow that verifies a clean working tree, checks for pending commits, and validates the correct branch and remote before transmission. Pre-push constraints and remote freshness checks help minimize mistakes.

What is the best way to prevent pushing unfinished work to a shared Git branch?▼

Preventing unfinished work from being pushed requires pre-push validation that enforces a clean working tree and confirms at least one commit exists. Safety checks also warn against pushing directly to main without review.

Can I push local changes directly to main in a collaborative development workflow?▼

You can push to main, but safe workflows warn against doing so without review. It is better to use feature branches and promote pull-request-based updates to ensure changes are reviewed before integration.

Why does Git reject my push and how do remote freshness checks work?▼

Git rejects a push when your local branch is not fresh against the remote. Remote freshness checks validate the branch and remote state, prompting you to fetch updates and resolve any divergence before transmitting your changes.

How do I verify my branch and remote before pushing committed changes?▼

Verifying your branch and remote involves safety checks that validate the current branch state and remote configuration. These governance steps guide correct branch usage and prompt for final confirmation before transmitting any updates.

Related Skills

Explore More Software Engineering Skills→
webdevcodywebdevcody
22

commit-push-and-release

Commit and push working-tree changes on main, then cut and push a minor version release tag.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
KiloforgeKiloforge
2

kf-conflict-resolver

Resolve git merge conflicts during push or pull sync operations.

Official
Advanced
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced