/ skills /changelog
Skill · Claude Code

changelog

A signed-in What's New page that gets a new entry every session

Use it when You want signed-in users to see what changed in your app, written from plain files, and want Claude to add an entry whenever it ships something they would notice.

Try it: paste this into Claude Code
Use the changelog skill to add a signed-in /changelog page to this app and log what we shipped today.
20 featuresPlain files you can edit by handVisible only to signed-in users

1What your users see

01

A What's New Page

A changelog page inside your app

Signed-in users get a /changelog page listing what changed and when. The skill is a spec, not a package: Claude builds the page in your own language and framework from its file format, parsing rules and behavior. People learn about new features from the app itself instead of an email they skipped.

02

A Timeline, Not a Wall

Entries hang off a timeline, one heading per day

Each day is a heading with a line running down its entries, one dot per change. Readers can scan the dates and stop where they last left off.

03

This Month Up Front

The main page shows only the current month

Older months move off the main page automatically as the calendar turns. The page stays short no matter how long you have been shipping.

04

Past Months, One Click

Each earlier month is a link with a count

Below the timeline, every past month appears as a link with how many entries it holds. You can see how busy each month was before opening it.

05

Back to Now

Each month page links back to the current one

Opening a past month shows only that month's entries, with a link back to the latest. Nobody gets lost in the archive.

06

Members Only

Signed-out visitors sign in, then land on the page

The page sits behind your existing sign-in. Someone signed out is sent to sign in and then taken straight to the changelog they asked for.

07

Rich Text in Entries

Bold text and links work inside an entry

Each bullet is written in markdown, so an entry can bold a feature name or link to its help page. Plain text works too.

08

One Per App

Each part of your app can have its own changelog

If your product has separate areas, each gets its own changelog at its own address and its own accent color. Shop customers don't wade through admin changes.

09

Graceful When Empty

A new app shows a calm 'nothing yet' message

Before the first entry exists, the page says Nothing here yet instead of an error. You can add the page on day one and fill it as you ship.

2Plain files behind it

10

Plain Markdown Files

One plain text file per app, newest first

Entries live in one markdown file per app, checked into your repo next to your code. Anyone can read, edit or review a change to it like any other file.

11

Nothing Gets Moved

Months are worked out when the page loads

The page sorts entries into months each time it renders, so nothing is ever moved to a separate archive file. There is no archive step to forget and no file that can quietly go missing.

12

A Bad Heading Won't Break It

An undated heading lands in its own Undated group

If someone writes a heading like Unreleased instead of a date, those entries show up under Undated rather than taking the page down.

13

Know What It Skips

The format is spelled out so nothing vanishes

Only date headings and top-level dash bullets are read. The skill says plainly that subheadings, nested bullets and intro text are skipped, so you know before an entry goes missing.

3The habit

14

An Entry Each Session

Claude adds a dated entry when it ships something

At the end of any session that shipped something users would notice, Claude adds an entry under today's date without being asked. The changelog stays current because nobody has to remember it.

15

Only What Users Notice

Features and real fixes, not tidy-up work

New features, redesigns and real bug fixes get an entry. Lint, refactors and typo fixes don't, so the page stays worth reading.

16

A Few Plain Bullets

One to three plain-language lines per day

Entries are short and written for users, not developers. If today already has a heading, Claude adds to it instead of starting a second one.

17

The Habit Is Written Down

A note in your project keeps future sessions on it

Setup adds a short section to your project's instructions file pointing at the changelog. Every future Claude session sees it and keeps the habit going.

4Built to last

18

Tests for the Quiet Bugs

Tests catch the bugs that fail without errors

Setup includes tests for the page, the sign-in gate, the month archive and the file parser, including a bad heading and text rendering outside its bullet. Those bugs would otherwise fail silently.

19

Colors That Survive the Build

Theme colors are spelled out so a CSS build keeps them

If your CSS tooling scans source files for complete class names, each color theme is written out as full class names rather than pieced together. A build that strips unused styles can then see them, so the timeline doesn't lose its colors in production.

20

Fits Your Stack

Swap in your own sign-in check and markdown tool

The page uses whatever sign-in check and markdown renderer your app already has, in whatever language it is written. Nothing new to adopt just for a changelog.