Generate and update the product changelog in Mintlify docs. Use when the user asks to update the changelog, add a changelog entry, document recent changes, or write release notes. Reads git history on main, filters to user-facing changes, and writes dated MDX files to docs/public/changelog/.
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Generate user-facing changelog entries from git history and write them as Mintlify MDX files.
Read .claude/skills/changelog/watermark for the last processed commit SHA. If the file is missing (first run), use the commit from 30 days ago as the starting point: git log --before="30 days ago" --format=%H -1 main.
Run git log --oneline --no-merges <watermark>..HEAD to get commits since the watermark. Read commit messages and changed files to understand the actual user-facing impact — don't just reword commit messages.
Group commits by their commit date (git log --format="%h %ad %s" --date=short). Each date that has user-facing changes gets its own entry file. Dates with only internal changes get no entry.
Include only changes visible to end users:
Exclude:
If there are no user-facing changes in the entire range, tell the user and stop.
Create one file per date at docs/public/changelog/YYYY-MM-DD.mdx, using the commit date (not today's date). If a file already exists for a date, regenerate it with the full set of commits for that day (not just new ones). Follow the references linked above for format, writing style, and hero vs. accordion decisions.
Add all new pages to the Changelog tab's pages array in docs/public/docs.json. List entries most recent first. The page path is changelog/YYYY-MM-DD (no .mdx extension).
Write the output of git rev-parse HEAD to .claude/skills/changelog/watermark.
If docs/public/changelog.mdx still exists as the old single-file changelog, delete it and remove its reference from docs/public/docs.json.
fkukuck/fabro
ac667f5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.