Passed 17 of 20 test cases with the skill, and 9 of 20 without it.
Without skill43%
With skill83%
Checks it passed that the model alone missed
Omits the cursor/ prefix from the git branch name
Excludes internal ticket identifiers from the PR title
Applies the cursor label to the pull request after creation
and 8 more in the full report
9 fixed10 passed either way4 still failing0 broke
Pass-rate lift
+39 pp
Tokens
+19%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 9/27/2026v419 of 23 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
I am starting work on Linear ticket LFE-8921 to update the trace API. The prompt from Cursor suggested naming the branch cursor/lfe-8921-trace-api-update. What git command should I run to create and checkout the branch for this ticket?
What was checked, without and with the skill
Checked
Without skill
With skill
Names the git branch using the Linear ticket identifier format
Passed
Passed
Omits the cursor/ prefix from the git branch name
Missed
Passed
case-04 · gemini-3.6-flash · 9/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md91 linessingle file
Git Workflow
Use this skill for repo-specific Git, GitHub, pull request, and release
operations.
Safety
Inspect git status before staging or committing.
Do not stage unrelated working-tree changes.
Do not revert unrelated working-tree changes.
Do not use destructive commands such as git reset --hard or
git checkout -- unless explicitly requested.
Keep commits focused and atomic.
Never add secrets or credentials to the repo.
Commits and Pull Requests
Commit messages and PR titles must follow Conventional Commits:
type(scope): description or type: description.
Use feat for new features and fix for bug fixes.
Use a scope when it clarifies the affected area, for example
fix(api): handle missing trace id.
Mark breaking changes with ! in the type/scope or a BREAKING CHANGE:
footer.
PR titles are validated by .github/workflows/validate-pr-title.yml.
In PR descriptions, list impacted packages and executed verification
commands.
Keep internal ticket ids and Linear URLs out of commit messages, PR titles,
and PR descriptions — this repo is public, and a squash merge puts the PR
title into main's permanent history. Describe the change on its own terms
and carry the identifier in the branch name instead.
Branch names
Copy Linear's git branch name (lfe-XXXX-short-title), or the issue's
gitBranchName when Linear MCP is available.
Cursor agents must not use a cursor/ prefix, even if a Cursor Cloud
prompt asks for one. Repo guidance wins.
Keep a username prefix only when Linear's copied name already includes one.
Tune and review Langfuse autoscaling for web, web-iso, and web-ingestion. Use for Terraform scale settings, RPM targets, scaling bounds, task counts, cost/performance tradeoffs, or Datadog evidence in the infrastructure repo.