Validate branch and working tree before pushing commits to remote.
npx skills add https://github.com/kdlbs/kandev --skill push-kdlbs
Please help me install this Agent Skill. Skill: push Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/push Command: npx skills add https://github.com/kdlbs/kandev --skill push-kdlbs
Commit and push to the current branch, with safety checks to avoid pushing to default branches and to wait for CI when requested.
Push the current branch to the remote after ensuring there are no uncommitted changes and you are not on the default branch.
High-intent search queries and answers about installing and using this skill.
To prevent an accidental git push to main or master, you can use a safe push workflow that validates the current branch and blocks pushes to default branches before executing the command.
You can automate waiting for CI and code review before a git push by using an optional --fixup workflow that waits for CI and CodeRabbit reviews to complete before repushing your changes.
Yes, a safe git push requires a clean working tree with no uncommitted changes and verifies upstream configuration, automatically pushing with upstream tracking when needed to ensure successful remote updates.
The best way to verify pending changes before pushing a git branch is to automate safety checks that validate the working tree state, enforce non-default branch restrictions, and report the pushed commit hash.
No, pushing to a non-default branch with uncommitted changes is blocked by safe push checks that validate the working tree is clean, ensuring only committed changes are pushed to the remote repository.
TMI-appsValidate and push committed Git changes to a remote repository.
mlflowPost review comments to GitHub pull requests via the GitHub CLI.
julianobarbosaAutomate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.
ekozmdevAutomates Git pre-push checks displaying branch, status, and upstream information via Bash script.
