skills.rest
entireio
entireioOFFICIAL
Explore all skills by this author →
Website𝕏@EntireHQGitHub

what-happened

Trace git blame provenance for code blocks with checkpoint-backed explanations.

208|14|Updated Apr 10, 2026
Search Tags:#debugging#code explanation#change history#git blame#code provenance#entire cli#commit context
One-click install
npx skills add https://github.com/entireio/skills --skill what-happened-entireio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: what-happened
Source: https://github.com/entireio/skills/tree/main/skills/what-happened
Command: npx skills add https://github.com/entireio/skills --skill what-happened-entireio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork of understanding why a specific code block was modified, solving the common frustration of encountering confusing or unexpected code with no clear context for its current form.

Core Features & Use Cases

  • Latest Change Provenance: Traces the most recent commit that modified a specific file line range or pasted code snippet using git blame and deduplicated entire explain lookups.
  • Checkpoint-Backed Context: Pulls associated agent session transcripts and checkpoints to explain the original problem, constraint, or decision that led to the code change.
  • Fallback Analysis: Provides a clear explanation of what the current code does when checkpoint history is unavailable, explicitly labeled as non-provenance data.
  • Use Case: For example, if you are confused about a 3-line rate-limiting block in your auth module, use this Skill to trace its last change, pull the original session context, and learn if it was added to fix a bug, handle an edge case, or meet a performance requirement.

Quick Start

Ask your agent "what happened here: [file-path]:[line-range]" to get a provenance-focused explanation of why a specific code block was last changed.

Frequently Asked Questions about what-happened

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

FAQPage Schema
How do I trace why a specific code block was changed in git?▼

To trace why a code block was changed in git, this Skill uses deduplicated git blame to find the latest commit, then pulls checkpoint context to explain the original problem or constraint that caused the modification.

What is the best way to find the commit context for confusing legacy code?▼

The best way to find commit context for confusing legacy code is running a deduplicated entire explain lookup on the file range, which retrieves the associated agent session transcripts to reveal the original decision.

Can I use pasted code snippets to find their change provenance?▼

Yes, you can use pasted code snippets to find their change provenance by passing the snippet to the Skill, which traces its latest modification history using git blame and entire explain lookups.

Do I need the Entire CLI to explain code provenance?▼

Yes, you need the Entire CLI to run deduplicated entire explain lookups and pull the checkpoint-backed session context required to explain the original problem that led to the code change.

What happens if checkpoint data is unavailable for a git commit?▼

If checkpoint data is unavailable, the Skill provides a fallback analysis explaining what the current code does, explicitly labeled as non-provenance data rather than the actual historical change context.

Does git blame show the original problem that caused a code modification?▼

Git blame shows the latest commit that modified a code block, but this Skill pairs it with entire explain lookups to pull the checkpoint transcript showing the actual original problem or constraint.

Related Skills

Explore More Software Engineering Skills→
CNifeCNife

git-master

Plan atomic commits, rewrite git history, and trace changes with safety checks.

Community
Advanced
noontide-conoontide-co
35

tool-dns

Catalog historical DNS tooling stubs and planned integration points.

Official
Basic
nicsuzornicsuzor
3

debug-headless

Capture and analyze AI CLI sessions in headless mode with Markdown transcripts.

Community
Intermediate
BSteffaniakBSteffaniak

commit-message

Generate a git commit message with title and description for current changes.

Community
Basic