Traces the rationale behind code changes from session transcripts and git history.
npx skills add https://github.com/psw7205/skills --skill trace-change-why-psw7205
Please help me install this Agent Skill. Skill: trace-change-why Source: https://github.com/psw7205/skills/tree/main/skills/trace-change-why Command: npx skills add https://github.com/psw7205/skills --skill trace-change-why-psw7205
git log, git blame, and code-context inference, explicitly labeling conclusions as verified facts versus inference. - Read-Only Investigation: Operates strictly as an analysis tool with no file modifications, and uses a helper script that handles session directory path encoding, multi-session matches, and large transcript files. - Use Case: You open a diff and wonder why a batch loader replaced eager loading. Ask why the change was made, and the Skill locates the session where the change happened, quotes the original request, and explains the design decision. ## Quick Start Ask why a specific file or line was changed, for example by saying "why was this function changed in src/api/loader.ts?"High-intent search queries and answers about installing and using this skill.
Point to the file or line and ask why it changed. The Skill searches Claude session transcripts for the Edit or Write call that made the change, then reads the surrounding conversation to recover the original request and reasoning.
The included find-session.sh script searches Claude transcript directories for the target filename, prints matching sessions with tool-call and context lines, and the Skill then reads the user and assistant messages around those matches.
The Skill falls back to git log, git blame, and code-context analysis to infer a plausible reason. Any conclusion not directly confirmed by a transcript or commit message is explicitly labeled as inference rather than fact.
No. The Skill is strictly read-only and forbids Edit and Write tool usage during investigation. It only reports findings, and any actual code modification requires a separate explicit request.
Rebase and squash operations rewrite history, so blame loses the original commit. The Skill compensates using git blame with -C -C flags to track moved code and git log -p --follow to trace changes across history rewrites.
a29paulRemove the /freeze edit scope restriction while preserving freeze hooks.
mengblomDocument major decisions with context and rationale in markdown records.
nilleReview code diffs for correctness, security, and conventions.
udecodeAnalyzes git history to trace code evolution, contributors, and change patterns.