github-commit-recovery

Recover deleted or orphaned GitHub commits with content, diffs, and metadata.

482|72|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/deonmenezes/mantishack --skill github-commit-recovery-deonmenezes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-commit-recovery
Source: https://github.com/deonmenezes/mantishack/tree/main/.claude/skills/oss-forensics/github-commit-recovery
Command: npx skills add https://github.com/deonmenezes/mantishack --skill github-commit-recovery-deonmenezes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub stores commits that may be deleted or orphaned; this Skill provides a way to recover their content, diffs, and metadata for forensic and auditing purposes.

Core Features & Use Cases

  • Retrieve full commit content, diffs, and metadata from GitHub using REST API, web access, or git fetch.
  • Verify authorship and history across repositories and forks, even for commits not on a current branch.
  • Use in security audits, incident response, and code provenance investigations.

Quick Start

Provide a commit SHA to retrieve the full commit content, diffs, and metadata from GitHub via REST API or the web interface.

Frequently Asked Questions about github-commit-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover deleted or orphaned GitHub commits?

You can recover deleted GitHub commits by supplying a commit SHA to retrieve content, diffs, and metadata via REST API calls, web interface access, or selective git fetch workflows.

What is the best way to retrieve lost commit metadata and diffs for a forensic investigation?

Retrieving lost commit metadata for forensic investigations involves querying orphaned commits by SHA to extract authorship, history, and file content across repositories and forks.

Can I use git fetch to pull a specific deleted commit from another fork?

Yes, you can use selective git fetch workflows to pull specific deleted commits from forks, verifying authorship and recovering lost changes not present on the current branch.

Does recovering orphaned commits via the GitHub REST API require authentication?

Recovering orphaned commits via the GitHub REST API includes authentication guidance to ensure proper access, alongside rate limit awareness for querying repositories and retrieving file content.

What are the limitations when auditing commit history for deleted changes across repositories?

Limitations when auditing commit history include GitHub API rate limits and the requirement to know specific commit SHAs to successfully retrieve deleted content, diffs, and metadata.