commit-and-push_skill

Overview

This skill creates atomic, conventional commits and pushes the current branch to the remote. It enforces Conventional Commits formatting so each change is small, focused, and traceable. The skill automates commit creation and performs a git push, adding upstream tracking if needed. It integrates with developer workflows to keep history clean and review-ready.

How this skill works

The skill invokes a /commit command to produce one or more commits that follow the Conventional Commits specification (type(scope): subject). Each commit is atomic and describes a single logical change. After committing, the skill runs git push, using -u origin <branch> when the branch has no upstream. It reports success or any git errors so you can resolve conflicts or authentication issues.

When to use it

• When you want clear, review-friendly history for a feature or bugfix.
• Before opening a pull request to ensure commits are small and descriptive.
• When multiple related changes must be split into separate logical commits.
• During automated workflows that require strict commit message formats.
• When pushing a newly created local branch that needs upstream tracking.

Best practices

• Make each commit atomic: one purpose, one change set.
• Use Conventional Commit types (feat, fix, docs, chore, refactor, test, perf).
• Include scope when helpful and keep the subject under 72 characters.
• Run tests and linters before committing to avoid broken history.
• Use -u origin <branch> only when you intend to set upstream for that branch.

Example use cases

• Split a large refactor into multiple feature and refactor commits for easier review.
• Create a fix commit for a failing test and push to trigger CI pipelines.
• Commit documentation updates separately using docs: scope messages.
• Push a newly created feature branch to origin with upstream tracking.
• Automate commit creation in a CI step that requires Conventional Commits for changelogs.