github-commit-recovery

Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing "deleted" commits that remain on GitHub servers.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-organized with genuinely domain-specific forensics content. Its weaknesses are a batch workflow missing validation/retry feedback loops and some inlined bulk content that could be externalized into reference files.

Suggestions

Add a validate/retry feedback loop to the batch-download pattern: on non-200, log the SHA and status, back off, and retry before skipping — this lifts workflow_clarity above the batch-operation cap of 3.

Move the complete API response JSON schemas and the Istio supply-chain case study into a separate references/ file referenced one level deep from the body, tightening conciseness and improving progressive_disclosure.

Condense the 'Response Structure' and authorship 'Response Analysis' JSON blocks to the key fields Claude needs, rather than reproducing full payloads.

Dimension	Reasoning	Score
Conciseness	Mostly efficient; the forensics-specific technique knowledge (deleted-commit URLs, rate-limit headers, short-SHA access) earns its place. Held at 4 rather than 5 because the full Istio narrative and complete JSON response bodies could be trimmed. Not a 3 because there is no generic concept padding Claude already knows.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: curl/git/jq one-liners and a runnable Python batch script with specific URLs and headers. Covers the common cases concretely.	5 / 5
Workflow Clarity	Methods are labeled and a troubleshooting section exists, but the batch-download Python pattern returns None on non-200 with no validation, retry, or error-recovery feedback loop. The rubric's batch-operation cap holds this at 3 rather than 4.	3 / 5
Progressive Disclosure	No bundle files exist; the skill is self-contained with well-organized sections and one-level external doc links. Held at 4 rather than 5 because bulk content (full API response schemas, the Istio case study) is inlined rather than split into one-level reference files.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person, concise, with explicit what/when triggers and a distinct niche. The only minor gap is a few natural trigger synonyms (force push, git history) that would round out keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'Recover deleted commits', 'using REST API, web interface, and git fetch', 'retrieve actual commit content, diffs, or patches' — for comprehensive coverage. Not below 5 because no concrete actions are missing; not above 5 as the scale caps at 5.	5 / 5
Completeness	Explicitly answers both what ('Recover deleted commits... retrieve actual commit content, diffs, or patches') and when ('Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches') with concrete trigger phrases. Cannot exceed the 5 anchor.	5 / 5
Trigger Term Quality	Good natural-keyword coverage with 'commit SHAs', 'diffs', 'patches', 'deleted commits'. Held at 4 rather than 5 because some common variations users say (e.g. 'force push', 'git history', 'force-pushed') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche — recovering deleted/force-pushed GitHub commits — with distinct triggers and minimal overlap with other skills. Not below 5 because the niche is unambiguous.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gadievron/raptor
Path: .claude/skills/oss-forensics/github-commit-recovery/SKILL.md
Commit: a5deef3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.