changelog · remocn — Claude Code skill: build a release video
changelog gathers changes from git tags, commits, or merged pull requests, writes them as short human-readable updates, and feeds them into a video template. Use it when you need a quick announcement video for a new version.
MIT 462 installs ★ 1,831 updated 2026-10-23
npx skills add Remocn/remocn --skill changelog -a claude-codeWhat changelog does
The changelog skill takes a range of commits—either you specify a version like v1.4.0, or it finds the latest tag and HEAD—and extracts what changed. It pulls from git log, merged pull requests (via GitHub CLI if available), or CHANGELOG.md in the repo itself.
Next, it picks 3–5 user-facing changes: drops refactors, dependency bumps, and CI work. Each change becomes one line, roughly 40 characters, framed from the user's side ("Vertical video for Shorts" instead of "feat(render): add preset"). It shows you the version and draft lines for review. Once approved, it passes everything to the video skill with the changelog archetype, which builds a storyboard, renders, and offers a Remocn Studio handoff.
Works across Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Requires git in PATH; gh CLI optional if you want to pull merged PR data from GitHub.
What it helps with
- extract changes between git tags into a release summary
- turn commit history into a one-liner per feature
- create a video announcement for a new software version
- identify what users actually care about in commit logs
Example prompts for the agent
- Make a changelog video for version v1.4.0
- What changed between v1.3.0 and v1.4.0—let's build the announcement
- Collect updates from the last two weeks and shoot a release teaser
How to install changelog
1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill changelog -a claude-code2Manually: put the files in place
~/.claude/skills/changelog/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/changelog/
1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill changelog -a codex2Manually: put the files in place
.agents/skills/changelog/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill changelog -a cursor2Manually: put the files in place
.cursor/skills/changelog/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Remocn/remocn plugins/remocn/skills/changelog2Manually: put the files in place
.github/skills/changelog/SKILL.md1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill changelog -a gemini-cli2Platform CLI
gemini skills install https://github.com/Remocn/remocn --path plugins/remocn/skills/changelogManually: put the files in place
.devin/skills/changelog/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Remocn/remocn --skill changelog -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about changelog
How do I install changelog for Claude Code?
Run npx skills add Remocn/remocn --skill changelog -a claude-code, then open ~/.claude/skills/changelog/SKILL.md.
What does the changelog skill do?
It reads git tags, commits, or merged PRs, picks the changes users will notice, writes them in two or three lines, and sends them to the video skill to produce a release video.
What do I need to use it?
You need git available in PATH. To pull merged pull request data from GitHub, also install the gh CLI.
Source text
SKILL.md · MIT
---
name: changelog
description: >
Turn a release into a short changelog video with remocn: collect what changed from git tags,
commits or merged pull requests, write it as a few human-readable lines, and build the video with
the changelog archetype. Use when the user wants a release, version or "what's new" video for a
repository.
---
# Changelog video
Range or release: $ARGUMENTS
## 1. Collect what changed
Work out the range: the argument if given (`v1.4.0`, `v1.3.0..v1.4.0`, "last 2 weeks"), else from
the latest tag to `HEAD`, else the last 30 days.
- Tags: `git tag --sort=-creatordate | head -5`
- Commits: `git log --no-merges --pretty='%s' <from>..<to>`
- Merged pull requests, when the GitHub CLI is available:
`gh pr list --state merged --search "merged:>=<date>" --json number,title,labels --limit 50`
- A `CHANGELOG.md` or release notes in the repo beat both. Prefer them when they cover the range.
## 2. Write the lines
The changelog archetype holds a version and a short list of changes. Video copy is not a commit log:
- Pick the 3–5 changes a user would notice. Drop chores, refactors, dependency bumps and CI.
- One line each, sentence case, under about 40 characters, starting with what the user gets
("Vertical video for Shorts and Reels", not "feat(render): add 9:16 preset").
- Group into New / Improved / Fixed only when there are enough lines to need it.
If you collected the lines from the repo, show the version and the lines and wait for edits before
building. If the user gave the changes themselves, tidy the wording and go straight on: the
storyboard the `video` skill shows next is where they confirm it, so don't stop twice.
## 3. Build
Run the `video` skill with the brief "changelog video for <product> <version>", the archetype
`changelog`, and the approved lines as content. It plans the storyboard, installs, composes, checks the
render and offers the Remocn Studio hand-off.
© Remocn · MIT · Remocn/remocn
Similar skills
All skills for Git and GitHub →changelog by other authors comes first.