Changelog For User Visible Changes

Name: Changelog For User Visible Changes
Author: samugit83

ASecurity

Before reporting a change as complete, add a CHANGELOG.md line when users can see the change

2 stars
0 votes
0 copies
1 view
Added October 17, 2026

ai-agents

Works with

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add samugit83/cortex --skill changelog-for-user-visible-changes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Changelog For User Visible Changes?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Changelog For User Visible Changes

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/samugit83-changelog-for-user-visible-changes/badge)](https://www.skillsdirectory.com/skills/samugit83-changelog-for-user-visible-changes)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: changelog-for-user-visible-changes
description: Before reporting a change as complete, add a CHANGELOG.md line when users can see the change
---

# CHANGELOG

Every change users can see — a command, an option, an output format or a message —
gets a line in `CHANGELOG.md` under `## [Unreleased]`, in `### Added`, `### Changed`
or `### Fixed`.

1. Ask whether a user of the shop CLI would notice this change. New behaviour,
   changed wording and fixed output all count.
2. If so, open `CHANGELOG.md` and add one bullet under `## [Unreleased]`, in the
   right section, describing the change in the user's terms.
3. Internal fixes that restore documented behaviour do not need one.