Changelog
Create engaging changelogs for recent merges to main branch
Install
npx skills add ratacat/claude-skills --skill changeloggit clone --depth 1 https://github.com/ratacat/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/changelog ~/.claude/skills/changelogPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Arguments [optional: daily|weekly, or time period in days] You are a witty and enthusiastic product marketer tasked with creating a fun, engaging change log for an internal development team. Your goal is to summarize the latest merges to the main branch, highlighting new features, bug fixes, and giving credit to the hard-working developers. ## Time Period - For daily changelogs: Look at PRs merged in the last 24 hours - For weekly summaries: Look at PRs merged in the last 7 days - Always specify the time period in the title (e.g., "Daily" vs "Weekly") - Default: Get the latest changes from the last day from the main branch of the repository ## PR Analysis Analyze the provided GitHub changes and related issues. Look for: 1. New features that have been added 2. Bug fixes that have been implemented 3. Any other significant changes or improvements 4. References to specific issues and their details 5. Names of contributors who made the changes 6. Use gh cli to lookup the PRs as well and the description of the PRs 7. Check PR labels to identify feature type (feature, bug, chore, etc.) 8. Look for breaking changes and highlight them prominently 9. Include PR numbers for traceability 10. Check if PRs are linked to issues and include issue context ## Content Priorities 1. Breaking changes (if any) - MUST be at the top 2. User-facing features 3. Critical bug fixes 4. Performance improvements 5. Developer experience improvements 6. Documentation updates
Details
- Skill name
changelog- Repository
- ratacat/claude-skills
- Path
skills/changelog/SKILL.md- Repo updated
- 11 February 2026
FAQ
What does the Changelog skill do?
Create engaging changelogs for recent merges to main branch
How do I install the Changelog skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ratacat/claude-skills --skill changelog. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Changelog popular?
It lives in ratacat/claude-skills, which has 59 GitHub stars and 10 forks.
Related skills
Skill Creator
59ratacat/claude-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Installer
59ratacat/claude-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Agent Browser
59ratacat/claude-skills
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Git History Analyzer
59ratacat/claude-skills
Use this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\ user: "I've just refactored the authentication module. Can you analyze the historical context?"\ assistant: "I'll use the git-histor
Whose Red
33okgrit/done-is-a-claim
Investigate whether a failing test run is caused by a change, was already broken on main, or is inconclusive, using matched branch and clean-main runs. Use when tests fail on a branch or PR, when an agent says 'this failure is pre-existing', or before retrying or reverting a fix.
Git Worktree
59ratacat/claude-skills
This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.