Block direct commits on protected branches during staging, committing, or pushing.
npx skills add https://github.com/tubtrb/autoreport --skill branch-commit-guard
Please help me install this Agent Skill. Skill: branch-commit-guard Source: https://github.com/tubtrb/autoreport/tree/main/codex/skills/branch-commit-guard Command: npx skills add https://github.com/tubtrb/autoreport --skill branch-commit-guard
This skill prevents direct commits on protected integration branches, reducing accidental changes and enforcing repository policy.
Run the guard script before staging or committing on protected branches to enforce safety and avoid accidental commits.
High-intent search queries and answers about installing and using this skill.
To prevent direct commits to protected git branches, use a guard script that intercepts staging, committing, or pushing actions and exits with a status code 2 to block routine modifications on integration branches.
You can allow an intentional commit to a protected branch by passing the explicit --allow-protected override flag to the guard script, bypassing the block for authorized integration work.
When a git branch guard blocks your commit, it exits with status 2 and suggests creating a child branch to isolate your development work away from the protected integration branch.
You should use a branch protection script in your devops workflow when you need to enforce repository policy proactively and reduce accidental changes to critical integration branches during routine development.
No, the branch-commit guard requires no external dependencies to run, as it operates as a standalone script to enforce branch safety and check protected branch names during your git workflow.
erclxGenerate and validate conventional git branch names with type and length constraints.
OpenAuthorityPush local branch commits to a remote Git repository.
baleen37Generate aligned pre-commit and CI templates with branch protection.
toqozCommit staged git changes with Conventional Commits and branch protection.
