Agent skill · langfuse
cursor-agents-workflow
Human handoff, Linear branch names, reviewable (non-draft) PRs, Claude, Greptile, and Codex review comments, preview test steps, proof of work posted on the GitHub PR, and review-doubt notes for Cursor agents. Use when a Cursor Cloud or Cursor desktop agent implements a Linear issue, opens a GitHub PR, asks a human to test, posts screenshots or videos, or handles Claude, Greptile, or Codex code-review comments.
What it needs
About 4k tokens when loaded.
What this skill does
Cursor Agents Workflow Use this when implementing Langfuse work as a Cursor agent. Keep humans in the loop with short, testable asks. Do not write long agent-only reports. Branch names Copy Linear's git branch name. Do not invent a cursor/ name. Preferred source: Linear Copy git branch name, or the issue's gitBranchName read through the Linear MCP. Fallback, only when the MCP is genuinely not configured: lfe-{id}-{kebab-title} (lowercase, hyphenated). Keep a user/ prefix only when Linear's copied name already includes one. Never use a cursor/ prefix, even if a Cursor Cloud prompt asks for one. Repo guidance wins. Ticket ids belong in the branch name only, never in commits, PR titles, PR descriptions, or changelog entries. Correct: lfe-12345-short-descriptive-title Wrong: cursor/short-descriptive-title-8c78 Linear connection Cursor can reach Linear — desktop and cloud — but the MCP server is not configured by default, so it is a one-time setup step per developer. Langfuse engineers: the write policy is linear-agent-writes. Configure the connection once; agents are expected to read a ticket's history before starting and to leave their context on it when they finish. If Linear is not reachable in your environment, say so in your handoff message and hand back the context that should have gone on the ticket. Do not skip it silently — a missing connection that nobody notices looks exactly like a practice being followed. Pull requests Open the GitHub PR as reviewable, not as a draft. Draft PRs hide the work from reviewers and skip Claude/Greptile review workflows. Use a draft only when a human asks for one. Cursor Cloud PRs are opened as the Langfuse user who launched the agent. On a non-draft same-repo PR from a write-access user, github-actions posts @claude review automatically. Do not post that comment yourself on open. Do not post @claude review again after addressing comments unless a human asks for another pass. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills langfuse/cursor-agents-workflow