git-pushing

Conventional commit automation stages all changes, generates a commit type and scope, creates a formatted message with attribution, and pushes to the remote in one step. This Skill uses a smart_commit.sh script that handles staging, message construction, and push procedures automatically, enforcing industry standards for commit hygiene.

Yes. The Skill pushes to GitHub repositories and automatically generates pull request links for new branches, eliminating manual branch tracking and PR creation steps. It works with conventional commits and handles remote synchronization including the -u flag for upstream tracking.

Use a smart commit script that stages changes, derives the commit type, generates a message, appends attribution, and pushes in one action. This approach reduces manual command execution, enforces consistent message formatting, and simplifies sharing completed features to GitHub.

No. The Skill automatically generates conventional commit messages by determining type and scope from your changes, then constructs concise, well-formatted messages with a Claude Code footer. Manual message construction is optional via a fallback path for environments without the script.

Conventional commits enforce a standard structure (type, scope, message) that improves commit history readability, enables automated changelog generation, and simplifies code review. This Skill automatically applies the convention, ensuring consistency across your repository without requiring developers to memorize syntax rules.

The Skill automatically sets the upstream tracking branch using the -u flag, synchronizes your local branch to the remote, and displays a GitHub pull request link for the new branch. This eliminates manual upstream configuration and streamlines the process of sharing new features.