github-sync

To commit and push code changes to a GitHub repository branch, this Skill stages all modified files, generates a conventional commit message from the diff, and pushes to the current branch while managing upstream tracking. It requires the git CLI for all operations.

Automating staging and pushing modified files to a remote GitHub branch is handled by staging all changes, creating commits with intelligently generated or user-provided messages, and executing the push operation while resolving non-fast-forward errors.

Yes, you need the git CLI installed to sync code with GitHub, as this Skill requires git CLI for all operations including staging modified files, generating conventional commit messages, and managing branch upstream operations.

Automated commit message generation works by analyzing the staged git diff to intelligently generate conventional commit messages, or it uses user-provided input to describe the code changes before pushing them to the GitHub repository branch.

When a non-fast-forward push error occurs during syncing to GitHub, this Skill manages the branch operations by providing guidance on handling merge conflicts and resolving the non-fast-forward push errors before completing the synchronization.

Yes, you can set the upstream branch when pushing code changes to GitHub, as this Skill manages branch operations including setting upstream tracking for the current branch during the push process to ensure your remote repository is synchronized.