commit-hard-push

To push to a protected git branch, this skill commits your changes and forces the push to the remote, bypassing protected-branch restrictions. It reads local project override files and OVERRIDES.md to apply safety rules before executing the push.

Yes, you can automate git commit and push with branch protection enabled. This skill applies per-skill or global override rules from local project files and OVERRIDES.md, then commits and pushes to the remote regardless of active branch protections.

Git branch protection overrides are defined rules that allow pushing to restricted branches. You need them when standard protections block direct remote pushes during iterative development, and this skill applies those overrides from OVERRIDES.md to ensure safe execution.

Configuring overrides for committing to protected branches involves creating local project override files and a plugin root OVERRIDES.md. The skill consults these files to absorb additional rules or exceptions, guiding safety checks before pushing changes to the remote.

Bypassing git branch protection removes standard review safeguards. While this skill follows defined override rules from OVERRIDES.md to maintain traceability, you should avoid using it for collaborative branches where peer review and CI validation are required before merging.

This git commit and push automation works without additional dependencies. It integrates with the harness plugin's common configurations and relies solely on local project override files and the OVERRIDES.md file to execute protected branch pushes safely.