mcpbeat

Changelog Writing

langfuse/changelog-writing

| Shared workflow for writing Langfuse changelog entries after a feature is complete. Use when a branch is ready for merge and a changelog entry or changelog draft is needed.

376 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
32482
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/langfuse/langfuse --skill changelog-writing

The instruction itself

6 sections, as written by the author

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
  • 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
  • Any docs pages that should be linked or created

Reference Files

  • Changelog destination: ../langfuse-docs/pages/changelog
  • Recent changelog examples: inspect 3-5 recent files in that directory
  • Existing docs: ../langfuse-docs/pages

How to use it

Copy the folder

Take langfuse/changelog-writing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.