git-commit-push_skill

Overview

This skill automates committing all repository changes with an auto-generated, context-aware commit message and pushes the result to origin. It inspects the working tree and recent commit style, enforces branch safety, avoids secrets, and follows repository commit conventions. The tool never accepts or uses user-supplied commit text or flags — it generates messages based on the actual diffs.

How this skill works

The skill first runs git status, git diff, and recent git log entries to understand what changed and how commits are styled. It refuses to proceed if there are no changes or if the current branch is main/master, and it warns about secret-like files, skipping them. It stages specific files by name, composes a concise message that respects commit conventions, commits using a heredoc to preserve formatting, then pushes with or without -u depending on upstream configuration.

When to use it

• You want a quick, consistent commit and push without typing a message.
• You need an auto-generated, descriptive commit that matches recent commit style.
• You want built-in checks for secrets and default-branch protection.
• You prefer staging specific files rather than bulk-add to avoid accidental commits.
• You want the push step to respect upstream tracking or set it safely when missing.

Best practices

• Run the command only when you want the tool to generate the commit message; do not append any message or flags — they will be ignored.
• Review the git status and diff output the tool presents before confirming staging and commit actions.
• Do not run this on main or master; create a feature branch first or use an interactive branch workflow.
• Keep secrets out of the repo; the tool will warn and skip files that resemble credentials.
• Prefer targeted staging of changed files to avoid committing unrelated artifacts.

Example use cases

• After finishing a local feature, use this to auto-generate a commit message and push the branch to origin.
• When you have multiple small fixes and want a concise, consistent commit that follows repository style.
• If you’re unsure how to phrase the commit, let the tool analyze diffs and recent commit messages and craft one.
• During rapid development to quickly push safe, non-secret changes while avoiding accidental commits to main.