Traces the latest change to a code block using git blame and Entire checkpoint lookups.
npx skills add https://github.com/squidllee/skills --skill what-happened-squidllee
Please help me install this Agent Skill. Skill: what-happened Source: https://github.com/squidllee/skills/tree/main/what-happened Command: npx skills add https://github.com/squidllee/skills --skill what-happened-squidllee
path:line, path:start-end, or a file path plus a pasted snippet, resolving exact line numbers before running any provenance commands. - Deduplicated Provenance Lookup: Groups blame blocks by unique commit and checkpoint, running entire checkpoint explain once per unique commit or checkpoint to avoid redundant lookups. - Explicit State Reporting: Distinguishes missing checkpoints, unavailable checkpoints, failed transcript lookups, uncommitted changes, and untracked files, with labeled fallback explanations of current code behavior when checkpoint context is unavailable. - Use Case: You see an odd conditional in cli/explain.go:103-107 and ask "why is this like this". The Skill blames the range, finds the commit, pulls the checkpoint transcript, and explains the bug or constraint that caused the change. ## Quick Start Ask the assistant to explain why the code at a specific file and line range looks the way it does, for example by saying "what happened at cmd/entire/cli/explain.go:103-107".High-intent search queries and answers about installing and using this skill.
Provide a file path with a line or range, such as path/to/file.go:103-107, and the Skill runs git blame on that range, then uses entire checkpoint explain to summarize why the most recent change was made.
Paste the snippet along with its file path. The Skill searches the file with fixed-string grep matching to locate the exact lines, converts the match to a line range, and then runs blame and checkpoint lookups on that range.
The Skill reports that no checkpoint was referenced and falls back to explaining what the current code does, clearly labeling the explanation as not checkpoint-backed rather than implying historical intent.
No. Uncommitted pseudo-commits and untracked files have no committed history, so the Skill marks those ranges accordingly and provides only a current-code behavior explanation without running checkpoint lookups.
Use what-happened for latest-change provenance on a specific block of code. For broad questions about the original intent of a symbol, file, or feature, the explain skill is the better fit.
MomoDavilukeInspect git state and execute narrow repository fixes with exact status reports.
SeongHuniRun a test-fix-retest loop to improve skills in Codex.
cin12211Refactor code by renaming symbols and extracting modules with impact analysis.
tisfengDraft Angular-style Git commit messages from staged changes.