branch-permissions

Automating Git branch permissions involves mapping specific branches like main or master to predefined rules that prompt for approval before changes. This Skill enforces those workflows using pre-tool use hooks based on your local configuration mappings.

Yes, you can auto-allow edits and pushes on feature branches while protecting the main branch. The Skill identifies your current branch and applies configurable permissions, automatically allowing actions on feature/ prefixes and prompting for approval on main.

Preventing accidental commits to the master branch requires enforcing explicit approval workflows for protected branches. This Skill maps your current branch to a predefined permission set and intercepts changes to main or master using pre-tool use hooks.

Yes, local configuration is required to set up branch-specific Git permissions. You must define local settings that map your branches, such as feature/ or main, to their corresponding permission sets for auto-allowed actions or explicit approval prompts.

A pre-tool use hook enforces code review rules by intercepting actions before execution and checking them against your branch permission mappings. It automatically allows safe commands on feature branches and requires explicit approval for changes on protected main or master branches.