Shared workflow for writing Langfuse changelog entries after a feature is complete.
SkillScore63Maintained
Automatic
◆Doc Ops pack
Last verified 9/27/2026
What it changes
Passed 13 of 21 test cases with the skill, and 7 of 21 without it.
Without skill33%
With skill63%
Checks it passed that the model alone missed
The changelog text excludes the identifier 'LFE-4019'.
The changelog entry text excludes the ticket identifier 'LFE-1294'.
The response lists documentation paths under `../langfuse-docs/pages`.
and 7 more in the full report
9 fixed6 passed either way7 still failing2 broke
Pass-rate lift
+29 pp
Tokens
+20%
Agent turns
0%
Response time
+15%
Model gemini-3.6-flashMeasured 9/27/2026v115 of 24 cases passed with skill · 21 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
Branch `lfe-4019-slack-alerts` addresses Linear issue LFE-4019 titled 'Slack webhook integration for alert thresholds'. The Linear issue discussion notes that webhook retries happen 3 times. Draft the changelog entry.
What was checked, without and with the skill
Checked
Without skill
With skill
The changelog text excludes the identifier 'LFE-4019'.
Missed
Passed
The changelog text excludes Linear URLs.
Passed
Passed
The changelog entry explains the Slack alert threshold notification feature for users.
Passed
Passed
case-18 · 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.md43 linessingle file
Changelog Writing
Use this skill when a completed feature branch needs a changelog entry.
Workflow
Understand the change set.
Study recent changelog patterns in ../langfuse-docs/pages/changelog.
Find related documentation links in ../langfuse-docs/pages.
Draft a user-focused changelog entry.
Recommend whether an image or screenshot should be added.
What To Gather
The branch diff relative to main
The Linear issue, if the branch name includes an lfe-XXXX identifier
The affected product areas
Relevant docs pages to link or create
Writing Rules
Write for users, not internal implementation detail
Never mention internal ticket ids or Linear URLs in the entry, even though
step 2 gathers the Linear issue for context
Prefer second person: "you can now..."
Focus on what changed, why it matters, and how to use it
Match the structure and tone of recent changelog posts
Keep technical detail only where it improves user understanding
Output Format
Provide:
A short summary of what changed
The complete changelog post content
Whether an image should be added and what it should show
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.