Agent skill · 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. Use when starting work on an existing feature, when planning multi-PR work, and always when wrapping up — "what happened to this screen before", "write the handover", "why is this code like this".
What it needs
About 4k tokens when loaded.
What this skill does
Linear context handover 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: 1. Before you touch a feature, reconstruct its history. Most "new" work on an existing surface has a paper trail that answers half the design questions. 2. When you wrap up, write the handover into the ticket's description. What an agent may write to Linear, which label stamps it, 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, and what a planning subticket must contain, are the sibling skill: linear-planning. Before you touch a feature: reconstruct its history 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: Everything up to the ticket ids is automatic. The ticket bodies need Linear: the script queries the API directly if LINEARAPIKEY is exported, and otherwise prints the ids, URLs and MCP calls for you to run — so the agent hand-off is the normal path, not a failure. By hand, the same chain is: 1. Code → PR. git log --follow <path> on the files you are about to change, then the commit's PR (gh api repos/<owner>/<repo>/commits/<sha>/pulls). 2. PR → ticket. The branch name carries the identifier (lfe-15489-release-to-everybody → LFE-15489). PR titles and descriptions in these repos deliberately omit ticket ids, so the branch is the only link. 3. Ticket → the rest. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills langfuse/linear-context-handover