git-commit-push

Commit changes with conventional commits format and push to the remote repository.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/generic-automation-and-it/smooth-ai-stockanalysis --skill git-commit-push-generic-automation-and-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-push
Source: https://github.com/generic-automation-and-it/smooth-ai-stockanalysis/tree/main/.agents/skills/git-commit-push
Command: npx skills add https://github.com/generic-automation-and-it/smooth-ai-stockanalysis --skill git-commit-push-generic-automation-and-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually staging changes, writing conventional commit messages, renaming branches to match naming policies, and pushing with correct upstream tracking involves repetitive git commands that are easy to get wrong. This Skill automates the commit-and-push sequence in one step. ## Core Features & Use Cases - Conventional Commits: Delegates change analysis, staging, and commit message generation to a low-cost sub-agent that follows the conventional commits format. - Branch Rename on Push: With --issue <number>, renames the local branch to the <type>/<issue>-short-description convention and pushes with upstream tracking in one step. - Graceful No-Op Handling: Treats "nothing to commit or push" as a normal outcome rather than an error, so chained workflows like PR updates continue uninterrupted. - Use Case: After finishing a feature, run the skill with --issue 42 to commit your work, rename the branch to something like feat/42-add-auth, and push it to origin ready for a pull request. ## Quick Start Ask the agent to commit my current changes with a conventional commit message and push them to the remote, renaming the branch for issue 42.

Frequently Asked Questions about git-commit-push

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

FAQPage Schema
How do I commit and push git changes in one step?▼

Invoke the skill with an optional commit message, and it checks for pending changes, delegates staging and conventional commit creation to a sub-agent, then pushes via a script that handles upstream tracking automatically.

How to rename a git branch to match an issue number before pushing?▼

Pass --issue followed by the issue number. The skill derives a conforming name in the format type/issue-short-description from the commit type and message, then renames the branch and pushes with --set-upstream in one step.

What happens when there is nothing to commit or push?▼

The skill treats an empty working tree or fully pushed branch as a graceful no-op, not an error. It reports the situation and continues, which allows chained workflows like PR description updates to proceed.

Does this skill create pull requests after pushing?▼

No, it only commits and pushes changes to the remote. For pull request creation or updates, use the separate git-commit-push-pr skill, which builds on this one's push behavior.

What is the --mansplain flag used for in git commits?▼

The --mansplain flag suppresses all interactive questions during the commit step. It is forwarded to the git-commit sub-agent, which then uses its best judgment for staging and message generation without asking the user.