git

Automating safe git commits and branches requires enforcing safety rules like conventional commit formats and preventing destructive actions. This skill applies safety protocols to local repositories to ensure reproducible workflows for automation agents.

Safety rules for git workflows in automation must prevent amending pushed commits, force-pushing to main/master, skipping pre-commit hooks, and committing secrets. This skill enforces these checks to mitigate risk during automated operations.

Yes, this git automation skill works with worktrees and rebases. It provides workflow guidelines covering branch hygiene, rebase versus merge strategies, and worktrees to maintain safe and consistent operations across local repositories.

To enforce conventional commits format in automated git operations, this skill applies strict formatting checks during the commit workflow. This ensures clarity and traceability for all automated commits in local repositories.

The best way to prevent destructive git actions in automation agents is applying a danger-zone checklist with clear prompts before risky operations. This skill enforces these risk mitigation checks to stop unsafe force-pushes and commits.

You should not use automated rebase and merge workflows when operating in defined danger zones without explicit safety checks. This skill uses a danger-zone checklist to identify limitations and prevent destructive actions during these specific git operations.