Support line targets and portable snippet search

c108fb4→main·

pfleidi·2mo ago·2 files·+7 added/-5 removed

Sessions

3187b04efcd3View 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-3187b04efcd3/index.html)

Changes

2

• MREADME.md+4/-2

• plugins/entire/skills/what-happened

• MSKILL.md+3/-3

39 unmodified lines

40
41
42
43
43
44
45
46
47
47
48
49
50
51
1 unmodified line

53
54
55
56
57
58
59

39 unmodified lines

### `what-happened`

Explains what happened to a specific code block by tracing the latest change for a file range or pasted snippet through git blame and Entire checkpoints.
Explains what happened to a specific code block by tracing the latest change for a file line,
range, or pasted snippet through git blame and Entire checkpoints.

Current behavior:

- resolves file ranges or pasted snippets to exact line numbers
- resolves file lines, ranges, or pasted snippets to exact line numbers
- groups matching blame ranges by unique commit before running `entire explain`
- summarizes `entire explain` output without dumping raw transcripts by default
- falls back to clearly labeled current-code analysis when checkpoint-backed context is unavailable
1 unmodified line

Examples:

- "what happened here: `src/auth.ts:42-57`"
- "what happened at `src/auth.ts:42`"
- "what happened to this block?" plus a pasted snippet

### `search`

MREADME.md+4/-2

rg -n -F "<distinctive snippet line>" -- <path>
grep -n -F -- "<distinctive snippet line>" <path>

• Read the small candidate windows around each hit, not the whole file unless the file is 120 unmodified lines

• Read the target block and the smallest necessary surrounding scope, such as the enclosing function, type, imports, or constants.

• Use rg to inspect direct call sites or definitions only when the block cannot be understood from local context.

• Use grep -n -F to inspect direct call sites or definitions only when the block cannot be understood from local context.

• Explain observable behavior, inputs, outputs, side effects, and important branches.

• Do not present this as historical intent, checkpoint rationale, or an agent transcript summary.

• State what cannot be known from current code alone.

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