What Happened
Explain why code looks the way it does by tracing the latest change for a file range or pasted snippet through `git blame` and deduplicated `entire checkpoint explain` lookups. Use when the user asks what happened, says "tell me why" about a code block, is confused about a section of code, asks "wtf is going on", "why is this like this", "why was this changed", or wants provenance for a specific file block.
Install
/plugin marketplace add entireio/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add entireio/skills --skill what-happenedgit clone --depth 1 https://github.com/entireio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/what-happened ~/.claude/skills/what-happenedPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# What Happened Use this skill when the user wants a provenance-focused explanation for a code block. Supported inputs: - `path:line` - `path:start-end` - `path` plus a pasted code snippet from that file If the user asks a vague provenance question without a file path, line range, or pasted snippet, ask for the target code and stop without running commands or using the header. ## Goal Find the most recent change blocks matching the user's target lines, list the matching commit hashes and checkpoint state, then summarize why each block was changed using the best available context. When checkpoint-backed context is unavailable, still explain what the current code does as an explicit fallback and clearly mark that explanation as not checkpoint-backed. ## Rules 1. Do not guess about file contents or line numbers. Resolve the exact target lines before explaining anything. 2. Use the installed `entire` binary from `PATH`, not `./entire` from the current repo. 3. Prefer `git blame` for provenance and `entire checkpoint explain --commit` for transcript-backed context. Do not use experimental `entire why` for this skill. 4. Use this skill for latest-change provenance on a specific block. For broad original intent of a symbol, file, or feature, prefer the `explain` skill. 5. Do not manually hunt through `.git/entire-sessions/` or raw transcript files for commit provenance. If `entire checkpoint explain` cannot provide transcript context, report the exact
Details
- Skill name
what-happened- Repository
- entireio/skills
- Path
skills/what-happened/SKILL.md- License
- MIT
- Repo updated
- 15 November 2026
FAQ
What does the What Happened skill do?
Explain why code looks the way it does by tracing the latest change for a file range or pasted snippet through `git blame` and deduplicated `entire checkpoint explain` lookups. Use when the user asks what happened, says "tell me why" about a code block, is confused about a section of code, asks "wtf is going on", "why is this like this", "why was this changed", or wants provenance for a specific file block.
How do I install the What Happened skill?
Claude Code plugin: /plugin marketplace add entireio/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is What Happened popular?
It lives in entireio/skills, which has 240 GitHub stars and 28 forks.
Related skills
Address Findings
240entireio/skills
Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` skill.
Explain
240entireio/skills
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.
Recall
240entireio/skills
Use when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook. Triggers on phrases like "have we done this before", "recall how we did X", "find similar work", "any precedent for", "has anyone solved", "is there a template for", and "how did we do this last time
Antfu
398JetBrains/skills
Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
Spark Python Data Source
407databricks/databricks-agent-skills
Build custom Python data sources for Apache Spark using the PySpark DataSource API — batch and streaming readers/writers for external systems. Use this skill whenever someone wants to connect Spark to an external system (database, API, message queue, custom protocol), build a Spark connector or plugin in Python, implement a DataSourceReader or DataSourceWriter, pull data from or push data to a system via Spark, or work with the PySpark DataSource API in any way. Even if they just say "read from X in Spark" or "write DataFrame to Y" and there's no native connector, this skill applies.
Betting
271machina-sports/sports-skills
Betting analysis — odds conversion, de-vigging, edge detection, Kelly criterion, arbitrage detection, parlay analysis, and line movement. Pure computation, no API calls. Works with odds from any source: ESPN (American odds), Polymarket (decimal probabilities), Kalshi (integer probabilities). Use when: user asks about bet sizing, expected value, edge analysis, Kelly criterion, arbitrage, parlays, line movement, odds conversion, or comparing odds across sources. Also use when you have odds from ESPN and a prediction market price and want to evaluate whether a bet has positive expected value. Don
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.