Changelog Writing Agent Skill
| 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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/langfuse/langfuse --skill changelog-writingThe instruction itself
6 sections, as written by the authorChangelog 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-XXXXidentifier - 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
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take langfuse/changelog-writing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.