skills.rest
oskarrough
oskarroughCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

arbe-changelog

Write user-facing changelog entries from development work and commit history.

Updated May 16, 2026
Search Tags:#changelog#versioning#documentation#writing#commits#release notes#summaries
One-click install
npx skills add https://github.com/oskarrough/robots --skill arbe-changelog-oskarrough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arbe-changelog
Source: https://github.com/oskarrough/robots/tree/main/skills/changelog
Command: npx skills add https://github.com/oskarrough/robots --skill arbe-changelog-oskarrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating raw development work into clear, user-facing changelog entries is hard: developers describe mechanisms instead of outcomes, include internal churn, and use inconsistent voice. This Skill turns commits, PRs, and changed files into concise release notes that users actually understand. ## Core Features & Use Cases - Entry Curation: Decides what belongs in a changelog, skipping internal churn and merging related implementation details into one user-visible entry. - Voice and Format Guidance: Enforces benefit-first, past-tense, verb-first bullets with no marketing language, file paths, or function names. - Release Workflow Integration: In arbe, adds each user-noticeable change as a bullet under ## [Unreleased] in docs/changelog.md within the same change, grouped under scope headings. - Use Case: After finishing a feature branch, ask the assistant to update the changelog; it inspects the commits and writes entries like "Added retry logic for CLI downloads" instead of "rewrote downloader." ## Quick Start Update the changelog with user-facing entries for the commits in my current change.

Frequently Asked Questions about arbe-changelog

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

FAQPage Schema
How do I write a good changelog entry from commits?▼

Inspect the commits enough to know the user-visible outcome, then write one sentence describing the destination, not the path. Lead with the benefit in past tense and active voice, like "Fixed login timeout," and drop work with no visible effect.

What should be included in a changelog?▼

Include user-facing changes, meaningful developer improvements, and frustration-killing fixes. Skip internal churn that does not change how someone uses, runs, debugs, or builds on the project.

Should bug fixes for unreleased features get their own changelog entry?▼

No. New features absorb their bug fixes within the same unreleased cycle, so the changelog just shows the working feature. A fix to something already released is its own entry.

When should I not use this changelog skill?▼

Do not use it for general documentation tasks; use a documentation skill instead. It is scoped to changelog entries, release notes, and sprint summaries, not README files or API docs.

What tense and voice should release notes use?▼

Past tense, active voice, and verb-first is the default, such as "Added retry logic for CLI downloads." Present tense is allowed when an entry describes how something now behaves and reads better that way.

Related Skills

Explore More Content & Communication Skills→
pascallammerspascallammers
1

changelog-generator

Generate changelogs from Git history, commit messages, and pull requests.

Community
Basic
dropseeddropseed
1.0k

plainx-release

Bump versions, generate changelogs, and tag Git releases for Python packages.

Official
Advanced
daominahdaominah

writing-style-markdown

Enforce Markdown conventions with bullet lists, Mermaid diagrams, and semantic line breaks.

Community
Basic
psengerpsenger
9

git-commit-pr-message

Generate conventional git commit messages, PR titles, and changelog entries from staged changes.

Community
Advanced