commit-push

Commits all repository changes and pushes the current non-default branch to origin.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill commit-push-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/commit-push
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill commit-push-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing local work on a feature branch requires careful Git sequencing: staging the full repository diff, validating the commit candidate, checking remote divergence, and pushing safely. This Skill automates that workflow while enforcing guardrails that prevent accidental pushes from the default branch, detached HEAD, or managed worktrees. ## Core Features & Use Cases - Whole-repo commit transaction: Stages the complete repository diff with repo-root git add -A through a claim-bound helper, reviews the candidate tree, and commits with normal hooks. - Safety-gated push: Verifies branch state, upstream configuration, remote divergence, and pre-push hooks before running a single non-force push to origin. - Idempotent behavior: Reports a no-op when the branch is clean and pushed, or pushes existing commits when the branch is ahead without creating empty commits. - Use Case: After finishing changes across multiple packages in a monorepo, invoke the Skill to commit everything with a generated message and push the feature branch, without risking a push from main or a diverged branch. ## Quick Start Ask the agent to run $commit-push to commit all current repository changes and push the active feature branch to origin.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I commit all repo changes and push a branch in one step?

Invoke $commit-push on your feature branch. It stages the complete repository diff with repo-root git add -A, validates the candidate, creates a commit with your message or a generated one, and pushes the branch to origin.

How to push a Git branch that has no upstream yet?

The Skill detects a missing upstream and runs git push -u origin HEAD:<branch> to publish the branch with tracking. It first confirms the branch is not the default branch and has commits or a diff relative to it.

Can I use this to create a pull request after pushing?

No, this Skill intentionally does not create, update, or merge pull requests. It only commits and pushes the current branch; use the separate create-pr skill for PR workflows.

Why does the push stop when a pre-push hook exists?

An active pre-push or reference-transaction hook has project effects the Skill cannot bound, so it stops instead of bypassing with --no-verify. You must resolve or own the hook explicitly before publishing.

What happens if my branch has diverged from origin?

The Skill stops and reports the divergence as a blocker. It never pulls, rebases, merges, or force-pushes; divergence recovery requires a separate explicit request.

Does it work from a subdirectory of a monorepo?

Yes, it resolves the repository root with git rev-parse --show-toplevel and always stages the full repo diff from there. The current working directory never narrows the commit scope.