linear-context-handover SKILL.md skillA

linear-context-handover from langfuse/langfuse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add langfuse/langfuse/linear-context-handover@git:20260911.a85d3ec

Pins git:20260911.a85d3ec in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
langfuse/langfuse
Path
.agents/skills/linear-context-handover/SKILL.md
Versions recorded
3
Latest version
git:20260911.a85d3ec, committed Sep 11, 2026
First version recorded
Sep 4, 2026
Size
6,877 bytes
Repository stars
37,634
License
a license file GitHub does not identify

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 splitting a large change, and always when wrapping up — "what happened to this screen before", "write the handover", "why is this code like this".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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, propose the handover for the ticket's description.**

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`](../linear-agent-writes/SKILL.md) 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.

## Before you touch a feature: reconstruct its history
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_g7o6mve2ug6bghpn/0020e853cddd275e788a070d1a7888b3b38af1095e4b5543d5bc387c30b3b489.json

Then /plugin install linear-context-handover@markdownregistry-g7o6mve2ug6bghpn in Claude Code. It installs git:20260911.a85d3ec, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add langfuse/langfuse/linear-context-handover@sha256:0020e853cddd275e

The line at the top of this page pins the label git:20260911.a85d3ec, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_g7o6mve2ug6bghpn.svg)](https://markdownregistry.com/a/art_g7o6mve2ug6bghpn)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in langfuse/langfuse/linear-context-handover since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of linear-context-handover from somewhere else? Ask it: where did my linear-context-handover come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between Sep 4, 2026 and Sep 11, 2026, about one every 3 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260911.a85d3ec latest2026-09-11 a85d3ec 6,877 BA view · diff
git:20260910.1acfa5d2026-09-10 1acfa5d 6,176 BA view · diff
git:20260904.0b8d7eb2026-09-04 0b8d7eb 6,139 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6877 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

langfuse/langfuse · 37,634 stars · license a license file GitHub does not identify · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_g7o6mve2ug6bghpn
GET https://markdownregistry.com/api/v1/resolve?ref=langfuse/langfuse/linear-context-handover
GET https://markdownregistry.com/api/v1/blob/0020e853cddd275e788a070d1a7888b3b38af1095e4b5543d5bc387c30b3b489

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from langfuse/langfuse

AGENTS.md@.agents AGENTS.md file
langfuse/langfuse · .agents/AGENTS.md
git:20261105.a869249 · audit A · 37,634 stars
add-model-price SKILL.md skill
langfuse/langfuse · .agents/skills/add-model-price/SKILL.md · Use when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing…
git:20261006.39cb678 · audit A · 37,634 stars
add-to-dependabot-csv SKILL.md skill
langfuse/langfuse · .agents/skills/add-to-dependabot-csv/SKILL.md · Append GitHub Dependabot or Snyk/code-scanning alerts to an existing vulnerability CSV after verifying their API…
git:20261002.3b02ae4 · audit A · 37,634 stars
agent-setup-maintenance SKILL.md skill
langfuse/langfuse · .agents/skills/agent-setup-maintenance/SKILL.md · Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared…
git:20260921.1357013 · audit A · 37,634 stars
analyze-cloud-costs SKILL.md skill
langfuse/langfuse · .agents/skills/analyze-cloud-costs/SKILL.md · Analyze Langfuse Cloud infrastructure cost structure using Metabase cost marts. Use when asked about cloud spend, AWS…
git:20260511.5e5ed8a · audit A · 37,634 stars
backend-dev-guidelines SKILL.md skill
langfuse/langfuse · .agents/skills/backend-dev-guidelines/SKILL.md · Build or review Langfuse backend code. Use for tRPC routers, public REST APIs, BullMQ processors, services, middleware…
git:20261105.4fa3d2e · audit B · 37,634 stars
changelog-writing SKILL.md skill
langfuse/langfuse · .agents/skills/changelog-writing/SKILL.md · Shared workflow for writing Langfuse changelog entries after a feature is complete. Use when a branch is ready for…
git:20260811.7617df6 · audit A · 37,634 stars
clickhouse-best-practices SKILL.md skill
langfuse/langfuse · .agents/skills/clickhouse-best-practices/SKILL.md · MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before…
v0.3.0 · audit A · 37,634 stars
code-review SKILL.md skill
langfuse/langfuse · .agents/skills/code-review/SKILL.md · Review Langfuse code changes for correctness, regressions, and best practices.
git:20261004.c37160d · audit A · 37,634 stars
create-repo-agent SKILL.md skill
langfuse/langfuse · .agents/skills/create-repo-agent/SKILL.md · Design, implement, review, or harden Langfuse repo-owned autonomous agents. Use for LLM-powered GitHub Actions…
git:20260729.6d2988f · audit A · 37,634 stars
cursor-agents-workflow SKILL.md skill
langfuse/langfuse · .agents/skills/cursor-agents-workflow/SKILL.md · Human handoff, Linear branch names, reviewable (non-draft) PRs, the `cursor` GitHub label, Claude, Greptile, and Codex…
git:20261105.a869249 · audit A · 37,634 stars
datadog-query-recipes SKILL.md skill
langfuse/langfuse · .agents/skills/datadog-query-recipes/SKILL.md · Research Langfuse production telemetry with reusable Datadog queries. Use for tenant or project activity, API usage…
git:20261119.d535d56 · audit A · 37,634 stars

Every file in langfuse/langfuse

Browse by kind, by grade A, or by owner.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.