changelog-generator
The changelog-generator skill analyzes git commit history to automatically generate user-friendly release notes by categorizing changes into features, improvements, bug fixes, and other logical groups while translating technical commit messages into clear customer language. Use this skill when preparing release notes, documenting weekly or monthly updates, writing app store submissions, or maintaining public changelogs to eliminate hours of manual changelog writing.
git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit /tmp/changelog-generator && cp -r /tmp/changelog-generator/.claude/skills/changelog-generator ~/.claude/skills/changelog-generatorSKILL.md
# Changelog Generator This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate. ## When to Use This Skill - Preparing release notes for a new version - Creating weekly or monthly product update summaries - Documenting changes for customers - Writing changelog entries for app store submissions - Generating update notifications - Creating internal release documentation - Maintaining a public changelog/product updates page ## What This Skill Does 1. **Scans Git History**: Analyzes commits from a specific time period or between versions 2. **Categorizes Changes**: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security) 3. **Translates Technical → User-Friendly**: Converts developer commits into customer language 4. **Formats Professionally**: Creates clean, structured changelog entries 5. **Filters Noise**: Excludes internal commits (refactoring, tests, etc.) 6. **Follows Best Practices**: Applies changelog guidelines and your brand voice ## How to Use ### Basic Usage From your project repository: ``` Create a changelog from commits since last release ``` ``` Generate changelog for all commits from the past week ``` ``` Create release notes for version 2.5.0 ``` ### With Specific Date Range ``` Create a changelog for all commits between March 1 and March 15 ``` ### With Custom Guidelines ``` Create a changelog for commits since v2.4.0, using my changelog guidelines from CHANGELOG_STYLE.md ``` ## Example **User**: "Create a changelog for commits from the past 7 days" **Output**: ```markdown # Updates - Week of March 10, 2024 ## ✨ New Features - **Team Workspaces**: Create separate workspaces for different projects. Invite team members and keep everything organized. - **Keyboard Shortcuts**: Press ? to see all available shortcuts. Navigate faster without touching your mouse. ## 🔧 Improvements - **Faster Sync**: Files now sync 2x faster across devices - **Better Search**: Search now includes file contents, not just titles ## 🐛 Fixes - Fixed issue where large images wouldn't upload - Resolved timezone confusion in scheduled posts - Corrected notification badge count ``` **Inspired by:** Manik Aggarwal's use case from Lenny's Newsletter ## Tips - Run from your git repository root - Specify date ranges for focused changelogs - Use your CHANGELOG_STYLE.md for consistent formatting - Review and adjust the generated changelog before publishing - Save output directly to CHANGELOG.md ## Related Use Cases - Creating GitHub release notes - Writing app store update descriptions - Generating email updates for users - Creating social media announcement posts
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Initialize Beads issue tracking in your project with interactive configuration setup.
Calculate priority score for bugs, issues, or tasks based on severity, impact, and likelihood. Use for bug prioritization, task ordering, or risk assessment.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Inline orchestration workflow for dead code detection and removal with Beads integration. Provides step-by-step phases for dead-code-hunter detection, priority-based cleanup with dead-code-remover, and verification cycles.
Analyzes code changes for bugs, security vulnerabilities, performance problems, and architectural improvements. Generates structured markdown reports with evidence-based findings tied to specific file:line references, and creates Beads tasks for tracking. Adapts review depth based on scope — from quick pre-commit checks to thorough branch reviews. Use proactively when reviewing code before commits, after implementing features, before PRs, when checking code quality, or when the user mentions "review", "check changes", "code review", "PR review", "review branch", or any code quality assessment.