github-commit-recovery

Recover deleted or force-pushed GitHub commits by SHA via REST API, web, or git fetch.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/roberttmadsen13-del/TOURney --skill github-commit-recovery-roberttmadsen13-del
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-commit-recovery
Source: https://github.com/roberttmadsen13-del/TOURney/tree/main/SKILLS/raptor-main/.claude/skills/oss-forensics/github-commit-recovery
Command: npx skills add https://github.com/roberttmadsen13-del/TOURney --skill github-commit-recovery-roberttmadsen13-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Access to content of commits that GitHub retains even after branches are deleted or overwritten, enabling retrieval of commit data, diffs, and patches for investigation or recovery.

Core Features & Use Cases

  • Web access to deleted commits via GitHub commit pages and patch/diff endpoints.
  • REST API access to fetch commit metadata, files, and diffs for forensic analysis.
  • Git fetch method to recover or inspect a specific commit in bulk or offline workflows.
  • Use cases include verifying authorship, auditing history, and recovering content after force-push events.

Quick Start

Fetch a specific deleted commit by SHA using the GitHub web interface, REST API, or a targeted git fetch to view its content.

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 commits from a force-pushed GitHub branch?

Recover deleted commits from a force-pushed branch by fetching the specific commit SHA using the GitHub REST API, web interface, or git fetch to access retained content and diffs.

Can I access the content of a dangling commit after a branch is deleted on GitHub?

Yes, dangling commits remain accessible on GitHub if you have the commit SHA. You can retrieve content, diffs, and patches via REST API endpoints or targeted git fetch for forensic analysis.

What is the best way to get a diff from an overwritten commit using the GitHub API?

Fetch commit metadata, files, and diffs from overwritten commits by querying the GitHub REST API with the specific commit SHA, enabling forensic historical audits and authorship verification.

Do I need authentication tokens to inspect deleted GitHub commits via the REST API?

Yes, accessing deleted commit content through the GitHub REST API requires authentication tokens along with the repository SHAs to authorize retrieval of commit data and patches.

Does git fetch work for recovering a specific deleted commit offline?

Git fetch supports recovering or inspecting specific deleted commits in bulk or offline workflows by targeting the exact commit SHA, allowing you to view retained content locally.

What are the limitations when recovering overwritten commits from GitHub?

Recovery of overwritten commits requires knowing the exact commit SHA beforehand; without the SHA, GitHub provides no native search mechanism to locate deleted or dangling commit data.