git-troubleshooter-c1edd2 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited git-troubleshooter-c1edd2 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Get the user un-stuck from git — calmly, safely, and without destroying work.
Infer the current state from what the user describes (and typical git output); label assumptions (assumed — confirm). Always give a concrete command sequence. If a step is destructive, say so loudly before it.
What happened / what they want (e.g. "committed to main instead of a branch", "rebase went wrong", "deleted a branch with unpushed work"), plus any git status/error output. Infer the rest.
One or two lines: what state the repo is in and why the user is stuck.
A numbered list of exact commands, each with a one-line note of what it does:
1. git reflog # find the lost commit's SHA
2. git checkout -b rescue <SHA> # recover it onto a new branchPrefer non-destructive routes (branch, reflog, --soft) over destructive ones. Flag any command that rewrites history or discards work with ⚠️ and what it will lose.
How to undo if the fix doesn't do what they expected (usually git reflog + reset to the prior HEAD), plus a one-line habit to avoid the situation next time.
git push --force, reset --hard, or clean -fd without a ⚠️ and a safer alternative firstgit reflog when work might be recoverable — it usually is~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.