- Home
- Skills
- Testing & Debugging
- ELYRAON Git Rescue
Works with the AI Agents you already use
ELYRAON Git Rescue
Diagnose broken Git states and produce the safest recovery path.
$7.99
About this skill
When a Git repository ends up in a confusing or damaged state, the dangerous move is to start typing commands. ELYRAON Git Rescue helps you understand what happened first, then gives you a recovery plan you review before anything changes.
It is a diagnostic and recovery-planning skill. It inspects your local repository with read-only Git commands and does not run recovery commands for you.
What it does
- State analysis reads the current HEAD, local tracking divergence, and repository conflicts.
- Reflog inspection extracts dangling commit IDs and lost-work candidates from your local history.
- Plan generation produces a structured list of recovery commands for you to review.
- Safety scoping keeps consequential actions such as reset or checkout behind your explicit approval.
- Evidence reporting separates verified Git state from recovery hypotheses, so you can see what is known and what is a guess.
How it works
- Point the skill at the local repository you need inspected.
- It runs read-only Git commands to collect reflog and status data. Hooks, fsmonitor, and global Git configs are disabled during inspection.
- It maps candidate commits to a recovery sequence and stages the commands as a plan.
- You review the plan and decide what to run or authorize.
Requirements
Python 3 and Git installed locally. Works on the repository on your machine, with no external services.
What it is not
It does not guarantee recovery, and it does not automatically run destructive commands, force-push, delete branches, or rewrite history. Reflog candidates are leads, not proof that all work can be restored. See Known Limitations.
Recovery depends on which Git objects and history still exist locally. Reflog availability varies, and commits that have been garbage-collected may be unrecoverable. Reflog candidates are leads, not a guarantee that all work can be restored, and recovery plans are not guarantees. Local state can differ from remote state. It does not automatically execute recovery commands: reset, checkout and similar actions are left to you and require your explicit approval. Destructive commands can cause data loss, so back up and verify before running any step. Hooks, fsmonitor and global Git configs are disabled during inspection. Some situations need human review, and there is no universal recovery guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Requires
Permissions
Terminal/Shell: runs read-only Git inspection commands and the bundled Python helper locally. Read Files: inspects the local repository state you point it at. Environment Variables: auto-detected from the package. No network access and no file writes; recovery commands are staged as a plan, not executed.