skills.rest
chicago-joe
chicago-joeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

what-happened

Correlate commits with provenance data to explain code changes.

Updated Jun 2, 2026
Search Tags:#debugging#commit#provenance#traceability#code-change#observations
One-click install
npx skills add https://github.com/chicago-joe/manymems --skill what-happened
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: what-happened
Source: https://github.com/chicago-joe/manymems/tree/main/plugin/skills/what-happened
Command: npx skills add https://github.com/chicago-joe/manymems --skill what-happened

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate why a code block changed by leveraging provenance data and session observations.

Core Features & Use Cases

  • Trace changes by correlating commits with provenance observations to explain why changes occurred.
  • Fetch code provenance for a given file and line to surface the exact changes and the session that produced them.
  • Provide a structured summary of the commit diff and related observations to guide debugging decisions.

Quick Start

Ask the AI to locate provenance for a given commit or file:line and summarize the related observations and decisions.

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 code change happened using provenance data?▼

To trace why a code change happened, you link specific commit SHAs or file:line references to provenance observations and session history. This retrieves the exact context and decisions that produced the modification.

What is code provenance and how does it help with debugging?▼

Code provenance is the recorded history linking commits to session-level observations. In debugging, it surfaces the exact file deltas and contextual decisions that explain why a specific code block was modified.

Can I find the session observations for a specific file and line number?▼

Yes, you can fetch code provenance by providing a file:line reference. This retrieves the session-level history and related observations that explain the changes made at that exact location.

What's the best way to retrieve a commit diff and related session observations?▼

Provide a commit SHA to retrieve the structured summary of the diff and related provenance observations. This correlates the exact code changes with the session context to guide debugging decisions.

Do I need access to provenance endpoints to trace code changes?▼

Yes, access to provenance endpoints and code provenance retrieval functions is required. These dependencies fetch the summaries, file deltas, and session-level history needed to analyze why changes occurred.

Related Skills

Explore More Software Engineering Skills→
dawsonblockdawsonblock

github-commit-recovery

Retrieve deleted GitHub commits by SHA via web, REST API, or git fetch.

Community
Advanced
Xza85hrfXza85hrf

receiving-code-review

Translate code-review comments into verified code changes with documented rationale.

Community
Intermediate
StrategicMilkStrategicMilk

Git Archaeology

Trace git history to uncover design decisions and regressions.

Community
Intermediate
phucle297phucle297

caveman-commit

Generate concise conventional commit messages for Git repositories.

Community
Intermediate