Dev Content Changelog Users Read

---
name: dev-content-changelog-users-read
description: "User-outcome phrasing, migration notes, and consistent categories building release trust."
---
# Write changelogs users read

> User-outcome phrasing, migration notes, and consistent categories building release trust.

**Track:** ✍️ Technical Writing · **Domain:** Dev Content & Advocacy · **Level:** foundation · **~20 min**

**Who this is for:** Technical Writers, Developer Advocates, Engineers Who Document, Content Leads

## When to Use This Skill

User-outcome phrasing, migration notes, and consistent categories building release trust.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Steps

1. Categorize: Added / Changed / Fixed / Breaking / Security only
2. Phrase entries as user outcomes, not commit messages
3. Breaking changes lead with migration snippet and deadline
4. Link each entry to PR/docs for depth-seekers
5. Keep voice consistent; assign one editor per release
6. Never ship silent dependency bumps past Security category

## Common Pitfalls

- 'Misc fixes and improvements' filler sections
- Breaking changes discovered at runtime

## Commands

**Install with skills CLI**
```bash
npx skills add aniruddhaadak80/skills --skill dev-content-changelog-users-read
```

**Install globally**
```bash
npx skills add aniruddhaadak80/skills --skill dev-content-changelog-users-read -g
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills