Install any skill in seconds. Free to start, no credit card required.
Get Started Free →langfuse/linear-context-handover
Use Linear as the org's memory: reconstruct a feature's history before touching it, and leave the reasoning behind finished work in the ticket description so the next agent inherits it.
Passed 20 of 21 test cases with the skill, and 8 of 21 without it.
and 14 more in the full report
13 fixed8 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
The history reconstruction script lf-context.sh can accept various identifier formats. What three artifact identifier types can be passed directly as command-line positional arguments to the script?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies file path as a valid positional argument to the script. | Missed | Passed |
The instructions your model reads when the skill loads.
Linear is the org's long-term memory. Agent sessions are not — they end, and everything they worked out ends with them. This skill is how reasoning survives the session that produced it.
Two halves, and the second one is the one people skip:
What an agent may write to Linear, which label stamps it, the propose-then-write
gate, and what stays human-only are not in this file:
linear-agent-writes is the authority. Read
it before your first write. This file is the craft — where post-context goes,
what earns a place in it, and the two mechanics that stop it being destroyed on
the way in.
How to slice a big change into PRs is ordinary judgment: prefer small reviewable PRs, and create subtickets under an existing parent freely when that helps. Reconstructing history is not by itself a reason to file a stack of subtickets.
Do this before designing anything. A reversal already litigated once does not need re-litigating.
Start with the CLI, which walks steps 1–3 for you and prints the ticket ids, the URLs and the exact MCP calls for step 4. Run it from inside the checkout you are about to change:
S=.agents/skills/linear-context-handover/scripts/lf-context.sh
bash $S web/src/features/experiments/.../ExperimentsTable.tsx
bash $S 65bbc753c # a sha · 16912 # a PR · LFE-15711 # a ticket
bash $S --help # options, and what is automatic
Everything up to the ticket ids is automatic. The ticket bodies need Linear: the
test cases passed, vs 8 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.