plain-prompt
Choose a safe Git recovery path
Distinguish working tree, index, local commits, published history, and reflog recovery.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Recommend the least destructive recovery matching repository state.
Context: Never rewrite shared history without explicit confirmation.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Repository state and collaboration:
{{environment}}
What happened:
{{evidence}}
Propose recovery steps.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
Accidentally reset --hard one local commit; nothing pushed; reflog shows HEAD@{1}Expected result
Create a safety branch at current HEAD, inspect `git show HEAD@{1}`, then recover with a new branch pointing to that reflog entry. No shared history rewrite is involved.