git-safe-workflow

You can prevent risky git pushes by applying guardrails that enforce non-destructive staging and branch safety checks. This workflow verifies the repository state and uses explicit prompts before executing commands, ensuring local development commits remain safe.

Managing git commits across multiple worktrees requires worktree safety guidance to avoid conflicts. The workflow performs non-destructive checks before staging to verify the current state, ensuring commits in one worktree do not negatively impact others.

A checkpoint commit workflow improves traceability by structuring commits into safe, verifiable stages. It performs non-destructive checks before staging and commits, creating a clear history of safe state changes throughout the development process.

You can execute risky git commands, but the workflow avoids them unless explicitly requested. It uses explicit user prompts for risky actions, ensuring destructive operations like force pushes are only performed with deliberate confirmation.

To guide a safe checkpoint commit, the workflow runs non-destructive checks to verify the repository state, stages changes safely, and explains any risks before committing. This structured approach prevents risky pushes and maintains branch safety.