changelog-narrator

Solid

Compare two document versions and produce a structured changelog — no git needed. Use for PRDs, SOPs, contracts, strategy docs. Triggers: 'compare these two documents', 'what changed between versions', 'generate a changelog', 'сравни две версии документа', 'что изменилось', 'сделай changelog'.

AI & Automation 14 stars 3 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
39
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Changelog Narrator This skill compares two versions of a business document and produces a structured, human-readable changelog — without git, CLI, or "Track Changes". Designed for non-technical users who receive updated drafts and need to understand what changed at a glance. **Input:** - Two local files (`.md` or `.txt`) in the Cowork workspace — old version (v1) and new version (v2) - Optional: version labels if filenames are ambiguous; optional focus area (e.g., "only compare Section 3") **Output:** - Markdown changelog: Summary → Added → Removed → Modified → Notes --- ## Language Detection Detect the user's language from their message: - If Russian (or contains Cyrillic): respond in Russian - If English (or other Latin-script language): respond in English - If ambiguous: respond in the language of the trigger phrase used --- ## Instructions ### Step 1: Identify and Validate Files 1. Check that exactly two files are provided - If only one file is given: stop — "Two documents are required. Please provide both the old version (v1) and the new version (v2)." - If no files are given: scan the Cowork workspace for `.md` and `.txt` files; list them and ask the user to specify which two to compare 2. Read both files - If a file is unreadable (binary, corrupted, unsupported format): stop — "Could not read [filename]. changelog-narrator works with .md and .txt files only." 3. Determine version order (which is v1, which is v2) - Infer from filename markers: ...

Details

Author
KirKruglov
Repository
KirKruglov/claude-skills-kit
Created
4 months ago
Last Updated
yesterday
Language
N/A
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

changelog-writer

Write external-facing changelog and release note entries in a pithy, tastefully sassy, occasionally clever voice that makes software updates fun to read without burying what actually shipped. Use this skill whenever someone asks to write, draft, or review a changelog entry, release notes, "what's new" post, or product update announcement for end users. Also trigger when someone pastes a list of shipped features/fixes and wants them turned into public-facing copy, or asks to make a changelog "less boring," "more fun," or "not sound like corporate speak."

21 Updated 4 days ago
ommakes
Web & Frontend Listed

changelog-generator

This skill should be used when the user asks to "generate a changelog", "create a changelog", "diff-based changelog", "changelog from git history", "release notes from commits", "what shipped in this repo", "write user-facing release notes", or wants a polished changelog built from a repository's entire git history by reading actual code diffs rather than trusting commit messages. Covers root commit through HEAD, classifies each change (feature/improvement/fix/security/breaking/internal), reads diffs as ground truth, dispatches per-range sub-agents for large histories, and emits emoji-grouped sections newest-first. Refuses date/version ranges - scope is always the whole history.

2 Updated 3 days ago
chrismccoy
AI & Automation Listed

writing-changelogs

Writes human-friendly changelog entries and release notes. Use when populating changelog, preparing releases, or reviewing release notes quality.

8 Updated today
dork-labs