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.