commit-push

Stage changes, create a conventional commit, and push to the remote branch.

8|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill commit-push-joecp17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/claude/skills/commit-push
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill commit-push-joecp17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of switching between checking git state, staging changes, writing a commit message, and then pushing to the remote branch.

Core Features & Use Cases

  • Creates a commit in a single workflow: Gathers repo context (status/diffs/recent log/branch tracking) and produces a conventional commit message that matches common types (feat, fix, refactor, docs, test, chore, perf, ci).
  • Stages safely and selectively: Uses the same “commit skill” rules—favoring specific file staging over broad git add -A, and skipping sensitive or unsuitable files like .env and credentials/large binaries.
  • Pushes with guardrails: Detects whether the branch has an upstream, handles new branch upstream setup, and stops to ask the user instead of force-pushing when the remote is ahead.

Quick Start

Use the commit-push skill whenever you say /commit-push to create a conventional commit for the appropriate staged changes and push them to your tracked (or newly created upstream) branch.

Frequently Asked Questions about commit-push

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

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

To commit and push changes in one step, this skill stages your current work, generates a conventional commit message, and pushes it to the correct tracked or newly created upstream branch.

How are conventional commit messages generated for git commits?

Conventional commit messages are generated by gathering repository context like diffs and recent logs, then matching the changes to common types such as feat, fix, refactor, docs, or chore.

How can I safely stage files and avoid committing sensitive data?

Safe staging favors specific file selection over broad git add -A, intentionally skipping sensitive or unsuitable files like .env, credentials, and large binaries to prevent accidental commits.

What happens if I push a local branch that is behind the remote?

When a local branch is behind the remote, the push is blocked and the skill asks the user for direction instead of executing a destructive force-push to overwrite remote changes.

How do I push a new Git branch and set up upstream tracking?

To push a new branch with upstream tracking, the skill detects the missing upstream configuration and automatically selects the correct push command to establish the remote tracking branch.