Does this skill support custom commit messages?

Yes, you can provide a specific custom message or allow the underlying script to handle the conventional formatting automatically.

Does it work with existing remote branches?

Yes, it pushes to the current branch and uses the -u flag to ensure the local branch is correctly tracked against the remote.

Which Git commands does this skill replace?

It replaces the manual sequence of git add, git commit, and git push by wrapping them into a single optimized automation script.

What are conventional commits?

Conventional commits are a lightweight convention for commit messages that provide an easy-to-read history for humans and automated tools (e.g., using 'feat:' or 'fix:').

Conventional Git Push & Sync

Name: Conventional Git Push & Sync
Author: pur3v4d3r

bypur3v4d3r

•

Developer Tools

Automates the staging, conventional committing, and pushing of code changes to remote repositories.

About

This skill streamlines the Git contribution process by handling the entire lifecycle of a code update—from staging modified files to pushing them to the remote server. It enforces conventional commit standards and automatically appends a Claude footer to commits, ensuring a clean and consistent project history while eliminating the need for manual, multi-step Git commands.

Key Features

Automated staging of all modified files
One-command push to remote with upstream tracking
Script-based execution to minimize manual command errors
Automatic Claude attribution footer in commit history
1 GitHub stars
Enforced conventional commit message formatting

Use Cases

Saving current progress to a remote repository during an active coding session
Maintaining a standardized commit history using conventional prefixes
Quickly pushing completed feature updates to GitHub or GitLab

About

Key Features

Automated staging of all modified files
One-command push to remote with upstream tracking
Script-based execution to minimize manual command errors
Automatic Claude attribution footer in commit history
1 GitHub stars
Enforced conventional commit message formatting

Use Cases

Saving current progress to a remote repository during an active coding session
Maintaining a standardized commit history using conventional prefixes
Quickly pushing completed feature updates to GitHub or GitLab