Changelog Automation
Unverified●36/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor·UnknownWe have not crawled the repo tree, so we will not guess
Codex·UnknownWe have not crawled the repo tree, so we will not guess
Gemini CLI·UnknownThe spec defines no detection rule for Gemini
Copilot·UnknownWe have not crawled the repo tree, so we will not guess
npx agentalley add changelog-automationWho is stuck, and on what
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
The whole source
Frontmatter — 2 properties
| name | changelog-automation |
|---|---|
| description | Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions. |
| 1 | --- |
| 2 | name: changelog-automation |
| 3 | description: Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions. |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # Changelog Automation |
| 7 | |
| 8 | Patterns and tools for automating changelog generation, release notes, and version management following industry standards. |
| 9 | |
| 10 | ## When to Use This Skill |
| 11 | |
| 12 | - Setting up automated changelog generation |
| 13 | - Implementing Conventional Commits |
| 14 | - Creating release note workflows |
| 15 | - Standardizing commit message formats |
| 16 | - Generating GitHub/GitLab release notes |
| 17 | - Managing semantic versioning |
| 18 | |
| 19 | ## Core Concepts |
| 20 | |
| 21 | ### 1. Keep a Changelog Format |
| 22 | |
| 23 | ```markdown |
| 24 | # Changelog |
| 25 | |
| 26 | All notable changes to this project will be documented in this file. |
| 27 | |
| 28 | The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), |
| 29 | and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). |
| 30 | |
| 31 | ## Detailed patterns and worked examples |
| 32 | |
| 33 | Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. |
| 34 | |
| 35 | ## Summary |
| 36 | |
| 37 | This release introduces dark mode support and improves checkout performance |
| 38 | by 40%. It also includes important security updates. |
| 39 | |
| 40 | ## Highlights |
| 41 | |
| 42 | ### 🌙 Dark Mode |
| 43 | |
| 44 | Users can now switch to dark mode from settings. The preference is |
| 45 | automatically saved and synced across devices. |
| 46 | |
| 47 | ### ⚡ Performance |
| 48 | |
| 49 | - Checkout flow is 40% faster |
| 50 | - Reduced bundle size by 15% |
| 51 | |
| 52 | ## Breaking Changes |
| 53 | |
| 54 | None in this release. |
| 55 | |
| 56 | ## Upgrade Guide |
| 57 | |
| 58 | No special steps required. Standard deployment process applies. |
| 59 | |
| 60 | ## Known Issues |
| 61 | |
| 62 | - Dark mode may flicker on initial load (fix scheduled for v2.1.1) |
| 63 | |
| 64 | ## Dependencies Updated |
| 65 | |
| 66 | | Package | From | To | Reason | |
| 67 | | ------- | ------- | ------- | ------------------------ | |
| 68 | | react | 18.2.0 | 18.3.0 | Performance improvements | |
| 69 | | lodash | 4.17.20 | 4.17.21 | Security patch | |
| 70 | ``` |
| 71 | |
| 72 | ## Commit Message Examples |
| 73 | |
| 74 | ```bash |
| 75 | # Feature with scope |
| 76 | feat(auth): add OAuth2 support for Google login |
| 77 | |
| 78 | # Bug fix with issue reference |
| 79 | fix(checkout): resolve race condition in payment processing |
| 80 | |
| 81 | Closes #123 |
| 82 | |
| 83 | # Breaking change |
| 84 | feat(api)!: change user endpoint response format |
| 85 | |
| 86 | BREAKING CHANGE: The user endpoint now returns `userId` instead of `id`. |
| 87 | Migration guide: Update all API consumers to use the new field name. |
| 88 | |
| 89 | # Multiple paragraphs |
| 90 | fix(database): handle connection timeouts gracefully |
| 91 | |
| 92 | Previously, connection timeouts would cause the entire request to fail |
| 93 | without retry. This change implements exponential backoff with up to |
| 94 | 3 retries before failing. |
| 95 | |
| 96 | The timeout threshold has been increased from 5s to 10s based on p99 |
| 97 | latency analysis. |
| 98 | |
| 99 | Fixes #456 |
| 100 | Reviewed-by: @alice |
| 101 | ``` |
| 102 | |
| 103 | ## Best Practices |
| 104 | |
| 105 | ### Do's |
| 106 | |
| 107 | - **Follow Conventional Commits** - Enables automation |
| 108 | - **Write clear messages** - Future you will thank you |
| 109 | - **Reference issues** - Link commits to tickets |
| 110 | - **Use scopes consistently** - Define team conventions |
| 111 | - **Automate releases** - Reduce manual errors |
| 112 | |
| 113 | ### Don'ts |
| 114 | |
| 115 | - **Don't mix changes** - One logical change per commit |
| 116 | - **Don't skip validation** - Use commitlint |
| 117 | - **Don't manual edit** - Generated changelogs only |
| 118 | - **Don't forget breaking changes** - Mark with `!` or footer |
| 119 | - **Don't ignore CI** - Validate commits in pipeline |
| 120 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Research Review via External Reviewer Backend (ultra reasoning)Get a deep critical review of research from an external reviewer backend (Codex or manual). Use when user says "review my research", "help me review", "get external review", or wants critical feedback on research ideas, papers, or experimental results.●····●38/40Training CheckPeriodically check WandB metrics during training to catch problems early (NaN, loss divergence, idle GPUs). Avoids wasting GPU hours on broken runs. Use when training is running and you want automated health checks.●····●37/40Hermes Tweet> Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.◐····●36/40Social Publishing> Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.◐····●34/40