git-mcp-workflow

Safe Git recovery requires an inspection-first workflow using git-mcp tools to assess status and history before mutating, ensuring you understand the repository state and avoid unsafe shell git commands during undo operations.

The best way to undo a git reset or detached HEAD is to apply a safety-ordered recovery sequence using git-mcp tools, which prioritizes reversible actions and protects published history during the restoration process.

Yes, you can use git-mcp tools for staging, rebasing, and cherry-picking. The workflow mandates using git-mcp equivalents for all Git mutations and inspections, enforcing shell git avoidance to prevent unsafe operations.

Safely rewriting Git history on a shared branch requires explicit guardrails; the workflow warns against risky published-history rewrites unless clearly approved, providing shared-vs-local history protection through git-mcp inspection tools.

Yes, git-mcp supports worktree management, release tagging, and LFS handling. It standardizes these Git Flow operations by requiring a context summary and targeted status inspection before executing any staging or branching mutations.

You should not use shell git commands for repository modifications when a git-mcp equivalent exists. The workflow enforces shell git avoidance to ensure inspection-before-mutation and apply safety-ordered undo and recovery processes.