# W Git Repair

> Resolve common Git problems and conflicts with inspected commands.

- Skill: `blockmatic/w-git-repair` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add blockmatic/w-git-repair`
- Raw SKILL.md: https://api.skillmd.com/api/skills/blockmatic/w-git-repair/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: blockmatic (https://skillmd.com/u/blockmatic)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/blockmatic/w-git-repair

---


Help with conflicts, detached HEAD, upstream divergence, and similar local Git problems. Follow [git publish](references/git-publish.md). Do not rewrite published history unless the user asked.

1. Inspect `git status`, `git branch -vv`, and the relevant log. State the current problem in one sentence.
2. Propose the smallest safe commands. Explain what they change. Require explicit confirmation before commands that can discard local changes (`git reset --hard`, `git clean`, `git restore`). Require an explicit user request before history-rewriting commands (`git rebase`, `git commit --amend` of a published commit).
3. After an authorized command, re-inspect status and remaining conflicts. Never force-push or bypass hooks.

