Deduplicate what-happened skill instructions

2e06a57→main·

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

Consolidate the fallback state taxonomy into a single canonical list in Rule 7, merge the two Response Format sections into one, remove the redundant snippet-resolution rule, and drop the duplicated ambiguous-snippet guidance from the response template.

Sessions

1fb1fe555aeaView 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-1fb1fe555aea/index.html)

Changes

1

• plugins/entire/skills/what-happened

• MSKILL.md+34/-45

12 unmodified lines

13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
16
17
18
23 unmodified lines

42
43
44
71
72
45
46
47
48
76
49
50
51
52
53
54
55
82
56
57
58
59
85
60
61
62
63
89
64
65
66
67
138 unmodified lines

206
207
208
234
235
236
237
238
239
240
241
242
209
210
211
212
213
7 unmodified lines

221
222
223
256
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
54 unmodified lines

306
307
308
317
318
319
309
310
311

12 unmodified lines

Use this skill when the user wants a provenance-focused explanation for a code block.

## Response Format

Begin the first successful resolved-code response to this skill invocation with the line:

`Entire What Happened:`

followed by a blank line, then the content.

- Apply the header to the **first successful resolved-code response of the invocation only.**
  If an earlier unresolved-input response omitted the header and the user later disambiguates
  the target, include the header on the resolved-code response. Do not re-print it on later
  follow-up turns within the same invocation.
- Do **not** include the header on unresolved-input responses (e.g. snippet not found,
  ambiguous snippet, invalid path or range). If the target code was resolved but no
  checkpoint-backed context exists, still use the header and clearly label the answer as
  current-code fallback analysis rather than a checkpoint summary.
- After the header, include exactly one short, original, non-lyrical "Tell me why" line
  randomly chosen from the examples below. Do not quote, paraphrase, or imitate Backstreet
  Boys lyrics or any other song lyrics.

Allowed examples:

- `Tell me why: the blame points here.`
- `Tell me why: the diff left a trail.`
- `Tell me why: the context starts here.`

Supported inputs:

- `path:line`
23 unmodified lines

5. Do not manually hunt through `.git/entire-sessions/` or raw transcript files for commit
   provenance. If `entire explain` cannot provide transcript context, report the exact
   missing or unavailable state.
6. If the user provides a snippet, resolve it to exact line numbers before explaining anything.
7. If multiple blame blocks match, include all distinct ranges. Deduplicate commit hashes
6. If multiple blame blocks match, include all distinct ranges. Deduplicate commit hashes
   before running `entire explain`; run transcript lookups once per unique commit, not once
   per range. Also deduplicate checkpoint IDs before expanding checkpoint transcripts; run
   checkpoint expansion once per unique checkpoint, not once per commit or range.
8. Distinguish these states explicitly:
7. Distinguish these states explicitly:
   - no checkpoint is referenced for the commit
   - a checkpoint is referenced but is unavailable locally or remotely
   - a checkpoint is available, but full transcript expansion failed and raw transcript
     expansion was not explicitly requested
   - Entire transcript lookup failed (the `entire explain` command itself errored)
   - the code is untracked, uncommitted, or otherwise has no committed history
9. For every resolved code block, include either checkpoint-backed history or a fallback
   - any other provenance command fails after the target code was resolved
8. For every resolved code block, include either checkpoint-backed history or a fallback
   explanation of what the current code does. Label fallback explanations as "not
   checkpoint-backed" and do not imply intent or historical rationale from checkpoints.
10. Treat `entire explain` command output as intermediate source material for summarization.
9. Treat `entire explain` command output as intermediate source material for summarization.
   Do not paste raw command output or full transcripts into the user response unless the user
   explicitly asks for raw output. Include only short error excerpts when they help the user fix
   a failed lookup.
11. Keep the final explanation concise and block-focused. Do not summarize unrelated parts
10. Keep the final explanation concise and block-focused. Do not summarize unrelated parts
   of the file.

## Workflow
138 unmodified lines

### 4. Add fallback code behavior analysis when needed

For any resolved range without a checkpoint-backed explanation, still answer what the current
code does. This applies when:

- the file is untracked
- the range is locally uncommitted
- no checkpoint is referenced for the commit
- the checkpoint is referenced but unavailable
- transcript lookup or expansion fails
- any other provenance command fails after the target code was resolved
For any resolved range that falls into one of the states listed in Rule 7 where
checkpoint-backed context is unavailable, still answer what the current code does.

Use only source-backed analysis:

7 unmodified lines

## Response format

Start with a short provenance summary:
Begin the first successful resolved-code response to this skill invocation with the line:

`Entire What Happened:`

followed by a blank line, then the content.

Allowed examples:

- `Tell me why: the blame points here.`
- `Tell me why: the diff left a trail.`
- `Tell me why: the context starts here.`

Start with a short provenance summary using one status per range from the states in Rule 7:

````text
Entire What Happened:
54 unmodified lines

When the input was a pasted snippet, include the resolved line range in the answer.

If the snippet matched multiple ranges and the user has not disambiguated them, do not continue
to transcript summarization. Present the candidate ranges and ask which one they want explained.

## Trigger phrases

This skill should trigger for questions like: