skills.rest
langfuse
langfuseOFFICIAL
Explore all skills by this author →
Website𝕏@langfuseGitHub

cursor-agents-workflow

Standardizes Linear branch naming, GitHub PR proof, and bot review handling for Cursor agents.

34.0k|3.7k|Updated May 18, 2023
Search Tags:#linear#cursor#Workflow#gitHub#Branch Naming#Code review#Pull request
One-click install
npx skills add https://github.com/langfuse/langfuse --skill cursor-agents-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cursor-agents-workflow
Source: https://github.com/langfuse/langfuse/tree/main/.agents/skills/cursor-agents-workflow
Command: npx skills add https://github.com/langfuse/langfuse --skill cursor-agents-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cursor agents working on Langfuse Linear issues often produce inconsistent branch names, draft PRs that hide work from reviewers, unresolved bot review threads, and proof of work that never reaches GitHub, forcing humans to reconstruct context.

Core Features & Use Cases

  • Branch Naming Rules: Enforces Linear's copied git branch name (e.g., lfe-12345-short-title) and forbids cursor/ prefixes and ticket ids in commits or PR titles.
  • PR and Bot Review Handling: Requires reviewable (non-draft) PRs and defines how to resolve Claude, Greptile, and Codex review comments without arguing or silently skipping findings.
  • Human Handoff and Proof of Work: Provides a TL;DR plus test-steps message format and rules for embedding screenshots or videos on the GitHub PR, plus a "what to doubt" comment naming risky decisions.
  • Use Case: A Cursor Cloud agent finishes a Linear ticket, opens a non-draft PR with embedded before/after screenshots, resolves Greptile threads, and posts a short comment telling the human exactly what to test and what to doubt.

Quick Start

Use the cursor-agents-workflow skill to implement this Linear issue, open a reviewable GitHub PR with proof of work, and prepare the human testing handoff.

Frequently Asked Questions about cursor-agents-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How should a Cursor agent name branches for Linear issues?▼

Copy Linear's git branch name directly, using the issue's gitBranchName when Linear MCP is available. The fallback format is lfe-{id}-{kebab-title}, and a cursor/ prefix must never be used even if a Cursor Cloud prompt suggests one.

How do I handle Claude, Greptile, or Codex review comments on a PR?▼

Keep each bot thread open without replying in it. If the finding is correct, apply the fix and resolve the thread; if you skip it, tell the human plainly what you skipped and why before resolving, never skipping quietly.

Should Cursor agents open draft or reviewable pull requests?▼

Open PRs as reviewable, not draft, because drafts hide work from reviewers and skip Claude and Greptile review workflows. Use a draft only when a human explicitly asks for one.

Where should proof of work screenshots be posted for a PR?▼

Post screenshots or videos on the GitHub PR itself, embedded in the PR body and repeated in the final comment when attributed to Cursor. Chat attachments alone are insufficient since reviewers look at GitHub.

When should the 'what to doubt' PR comment be skipped?▼

Skip it when the comment would be attributed to a human author rather than Cursor, such as with Claude Code or other tools commenting as the authenticated user. Docs-only changes can also skip proof artifacts.

Related Skills

Explore More Software Engineering Skills→
NIMBUS-MXNIMBUS-MX

ticket-brief

Generate work briefs with goals, acceptance criteria, and commit prefixes from ClickUp, Linear, GitHub tickets.

Official
Intermediate
catu-aicatu-ai
12

harness-land

Merge an approved pull request after confirming an archived harness plan.

Official
Intermediate
ilamanovilamanov

review-loop

Automate pull request preparation, AI review, and submission in GitHub repositories.

Community
Advanced
pbuchmanpbuchman
8

nitpick-nuker

Automate GitHub PR review comment triage and fix actionable feedback until CI passes.

Community
Advanced