Skip to content

← Aman Kumar Limited · RegisterNotes to the accounts · SHPL

Flagship segment · oss · 2026 · Shipped

Shiplog

Changelogs people actually read. Turns git history into release notes covering what changed, who it affects and what they need to do.

Role
Solo — design, code, docs
Solo
Outcome
Open source, v0.3.0. Tested on JS/TS, Python, Go, Java/Kotlin, C#, PHP, Ruby and Rust repos.
Stack
Python 3.10+ stdlib · Claude Code skill · Atom/JSON feeds · Slack

Problem

Teams ship a lot and most of it goes unnoticed. The changelog that does exist says "refactor auth middleware". Support learns about changes from tickets.

What I built

  • A Claude Code skill and plugin. Claude drafts each entry from commits and PRs. When it can't infer the impact, it asks once, in a single message.
  • Every entry must answer three questions: what changed, who is affected, and what they need to do.
  • Outputs: an accessible changelog page, an Atom feed per audience, a JSON feed and CHANGELOG.md, with optional Slack announcements.
  • Works on one app or a monorepo. It appends to existing changelogs in their own format.
  • A CI gate that blocks release tags with no complete entry.

Under the hood

git commits + PRs
collect_changes.py
Claude drafts
validate.py
render.py / changelog_md.py
page · feeds · CHANGELOG.md
notify.py (Slack)
git commits + PRs → collect_changes.py → Claude drafts → validate.py → render.py / changelog_md.py → page · feeds · CHANGELOG.md → notify.py (Slack)

Risk factors

  • Young project: 13 commits and v0.3. Tested on eight languages, but real-world usage is still small.

This is a portfolio, not an offer of securities. No shares exist. Figures are about shipped work.