Avoid redundant what-happened snippet reads

c6ea5eb→main·

pfleidi·2mo ago·1 file·+3 added/-2 removed

Sessions

ac192f0ce538View transcript

[?
I have added a new skill to plugins/entire/skills/what-happenedCodex·GPT-5.5·1 step](/content/gh/entireio/skills/session/019dc0d3-6b22-7052-b168-4487a38e0f4d#timeline-ac192f0ce538/index.html)

Changes

1

• plugins/entire/skills/what-happened

• MSKILL.md+3/-2

138 unmodified lines

139
140
141
142
143
142
143
144
145
146
147

138 unmodified lines

Build a map from commit SHA to all target ranges blamed to that commit. Do not run
`entire explain` separately for multiple ranges that share the same commit.

After resolving the matching ranges, read the file contents for each matched block and keep
the exact snippet so the final answer can show users which code each provenance entry refers to.
Keep the exact snippets from the target-resolution read so the final answer can show users
which code each provenance entry refers to. Only reread a matched block if the snippet for
that range was not already captured.

### 3. Explain each unique commit

Mplugins/entire/skills/what-happened/SKILL.md+3/-2