skills.rest
AgentSystemLabs
AgentSystemLabsOFFICIAL
Explore all skills by this author →
GitHub

commit-and-push

Commit local changes and push the current HEAD branch to its remote.

121|2|Updated Apr 24, 2026
Search Tags:#git#commit#push#upstream tracking#release risk#code quality gate#no force push
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill commit-and-push-agentsystemlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-and-push
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/commit-and-push
Command: npx skills add https://github.com/AgentSystemLabs/core --skill commit-and-push-agentsystemlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the risk and friction of manually committing changes and then pushing them to the correct remote branch by bundling both actions into one guarded workflow.

Core Features & Use Cases

  • Production-ready commit composition: Delegates commit creation to the commit skill, including its pre-flight quality gate, and never re-implements commit grouping.
  • Upstream-aware, no-force publishing: Pushes the current HEAD branch, sets upstream when missing, and never force-pushes; it stops on rejected pushes and guides the user to rebase via git pull --rebase.
  • Risk and readiness checks: Runs mandatory check-pr-readiness for fast/balanced, and runs check-release-risk as a non-blocking briefing before git push.

Quick Start

Use it when you want to commit your current work and push it to the remote in one step after you’ve made changes on your current branch.

Frequently Asked Questions about commit-and-push

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

FAQPage Schema
How do I commit and push local git changes to a remote branch in one step?▼

To commit and push local git changes, this workflow runs a pre-flight quality gate to group commits, then pushes the current HEAD branch to its remote while automatically setting upstream tracking if missing.

Can I force push with git when my remote branch is rejected?▼

No, this git push workflow refuses force-push execution. If a push is rejected, it stops and guides you to resolve conflicts by running git pull --rebase instead of overriding remote history.

What git quality gates and release risk checks run before pushing code?▼

Before pushing code, the workflow runs a mandatory PR readiness check for fast and balanced modes, and performs a non-blocking release-risk briefing to evaluate production impact prior to executing git push.

How does upstream tracking detection work when pushing a new git branch?▼

Upstream tracking detection uses the @{u} reference to verify the current branch's remote link. If upstream tracking is missing, the push command automatically sets it to the correct remote branch.

Does this git commit and push workflow run if I have zero local changes?▼

No, the workflow refuses push-after-zero-commits execution. It requires the commit step to run first, ensuring there are actual grouped production-ready changes before publishing to the remote.

Related Skills

Explore More Software Engineering Skills→
webdevcodywebdevcody
22

commit-and-push

Commit staged changes and push the current branch to its upstream.

Community
Intermediate
mkalkeremkalkere
4

pr-create

Create GitHub pull requests and request code reviews from feature branches.

Community
Advanced
linskybinglinskybing

production-readiness-checklist

Enforce code quality and deployment checks before releases.

Community
Basic
jokken79jokken79
1

git-pushing

Stage, commit, and push git changes with conventional commit messages.

Community
Intermediate