Stage all changes, commit with conventional prefixes, and push to the current branch.
npx skills add https://github.com/heyAyushh/stacc --skill commit-push
Please help me install this Agent Skill. Skill: commit-push Source: https://github.com/heyAyushh/stacc/tree/main/configs/commands/skills/commit-push Command: npx skills add https://github.com/heyAyushh/stacc --skill commit-push
This Skill addresses the need to reliably commit local changes and push to the current branch while preventing accidental pushes to protected branches like main or master. It standardizes the workflow to reduce mistakes and improve collaboration.
Use the commit-push skill to commit all changes on the current branch and push to the corresponding remote branch with protection against main/master. MSG="fix: concise message" BRANCH=$(git branch --show-current) if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then echo "Direct pushes to main/master not allowed"; exit 1; fi git add -A git commit -m "$MSG" git push -u origin "$BRANCH"
High-intent search queries and answers about installing and using this skill.
Automating a git commit and push with branch protection stages all changes with git add, creates a conventional commit message, and blocks pushes to main or master by checking the current branch before pushing to origin with upstream tracking.
The safest commit and push workflow checks the current branch against main or master, stages all modifications with git add -A, commits using conventional prefixes like fix or feat, and pushes to origin with upstream tracking enabled.
Yes, pushing to origin without updating master is possible by validating the current branch name before execution; if the branch is main or master, the operation aborts to enforce branch protection rules during collaboration.
Setting upstream tracking automatically during a push uses the git push -u origin command with the current branch name, linking the local branch to the remote repository and simplifying future updates.
No external dependencies are required; the commit and push workflow operates using standard git commands available in local repositories, making it suitable for collaboration setups without additional installed packages.
Using conventional commit prefixes like fix or feat when pushing to a protected branch standardizes commit history, improves collaboration readability, and ensures structured updates across guarded remote branches.
gajjalaashok75-UIStages modified files, commits conventionally, and pushes to remote tracking repository.
sumrae412Automate conventional commits, pull requests, and 10-step code review before merging.
helderbertoStage all Git changes, generate a commit message, and push to the current branch.
facebookScript Git interactive rebases using GIT_SEQUENCE_EDITOR and --exec.
