Skip to content
Agentmart
Submit a tool

writing-changelog

Writes a Keep a Changelog entry from a description of changes or a git log.

Skill by matthewhand

IndexedMIT★ 20
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/matthewhand-writing-changelog

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Writes a Keep a Changelog entry from a description of changes or a git log. Use when the user asks for a changelog entry, release notes, or mentions updating CHANGELOG.md.

Use cases: writing, productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/writing-changelog

What's inside

Skill name
writing-changelog
Description
Writes a Keep a Changelog entry from a description of changes or a git log. Use when the user asks for a changelog entry, release notes, or mentions updating CHANGELOG.md.
License
MIT
Instructions
33 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Writing a Changelog Entry

Produce a [Keep a Changelog](https://keepachangelog.com) entry for the changes
described. Write for a human reader deciding whether to upgrade — lead with
impact, not implementation.

## Rules

- Group items under these headings only, in this order, omitting empty ones:
  `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`.
- One bullet per user-visible change, imperative mood, present tense
  ("Add X", "Fix Y") — not "Added"/"Fixed" in the bullet itself.
- Describe the effect on the user; mention internals only when they change
  behavior. Collapse purely internal refactors into one line or omit them.
- Reference issues/PRs as `(#123)` when given. No author handles, no dates
  inside bullets.

## Output template

```
## [<version>] - <YYYY-MM-DD>

### Added
- <new capability and why it matters> (#NN)

### Fixed
- <the bug, stated as the symptom the user saw> (#NN)
```

Output only the entry. If a version or date is unknown, use `[Unreleased]` and
omit the date.

From matthewhand/operating-swarm, MIT.

More from matthewhand/operating-swarm

Signals

Stars
20
Forks
6
Open issues
1
Last commit (this folder)
Jun 17, 2026 (4 months ago)
Last release
Jun 19, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/matthewhand/operating-swarm
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from matthewhand

Cite this page

writing-changelog skill. Agent Mart. https://agentmart.dev/skills/matthewhand-writing-changelog (last updated 2026-10-24)