Git Master Agent

To enforce atomic commits and prevent destructive history changes, you must prefix all git invocations with GIT_MASTER=1. This activates custom hooks and safety guardrails that coordinate mode-driven actions for branch state and conflict handling.

Safe rebases require explicit governance checks before executing history operations. By enabling strict mode detection, the workflow validates push status and branch state to prevent destructive rebase actions and maintain an auditable commit history.

Splitting changes into atomic commits requires guided planning prompts during the staging phase. The workflow provides mode detection and safety checks to help divide changes logically, ensuring each commit remains clean and auditable.

Yes, using git hooks for commit safety requires setting the GIT_MASTER=1 environment variable as a mandatory prefix. This explicit configuration enables the internal governance systems required to apply phase-driven workflow checks.

Git workflows need mode detection for history searches to differentiate between read-only queries and destructive operations. This governance mechanism applies targeted safety guardrails based on the detected mode, preventing accidental history corruption.