Name: changelog-automation
Author: wshobson

Imported from wshobson/agents (plugins/documentation-generation/skills/changelog-automation/SKILL.md) via skills.sh. Install upstream with npx skills add wshobson/agents --skill changelog-automation. Copyright stays with the author.

Changelog Automation

Patterns and tools for automating changelog generation, release notes, and version management following industry standards.

When to Use This Skill

Setting up automated changelog generation
Implementing Conventional Commits
Creating release note workflows
Standardizing commit message formats
Generating GitHub/GitLab release notes
Managing semantic versioning

Core Concepts

1. Keep a Changelog Format

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

## Summary

This release introduces dark mode support and improves checkout performance
by 40%. It also includes important security updates.

## Highlights

### 🌙 Dark Mode

Users can now switch to dark mode from settings. The preference is
automatically saved and synced across devices.

### ⚡ Performance

- Checkout flow is 40% faster
- Reduced bundle size by 15%

## Breaking Changes

None in this release.

## Upgrade Guide

No special steps required. Standard deployment process applies.

## Known Issues

- Dark mode may flicker on initial load (fix scheduled for v2.1.1)

## Dependencies Updated

| Package | From    | To      | Reason                   |
| ------- | ------- | ------- | ------------------------ |
| react   | 18.2.0  | 18.3.0  | Performance improvements |
| lodash  | 4.17.20 | 4.17.21 | Security patch           |

Commit Message Examples

# Feature with scope
feat(auth): add OAuth2 support for Google login

# Bug fix with issue reference
fix(checkout): resolve race condition in payment processing

Closes #123

# Breaking change
feat(api)!: change user endpoint response format

BREAKING CHANGE: The user endpoint now returns `userId` instead of `id`.
Migration guide: Update all API consumers to use the new field name.

# Multiple paragraphs
fix(database): handle connection timeouts gracefully

Previously, connection timeouts would cause the entire request to fail
without retry. This change implements exponential backoff with up to
3 retries before failing.

The timeout threshold has been increased from 5s to 10s based on p99
latency analysis.

Fixes #456
Reviewed-by: @alice

Best Practices

Do's

Follow Conventional Commits - Enables automation
Write clear messages - Future you will thank you
Reference issues - Link commits to tickets
Use scopes consistently - Define team conventions
Automate releases - Reduce manual errors

Don'ts

Don't mix changes - One logical change per commit
Don't skip validation - Use commitlint
Don't manual edit - Generated changelogs only
Don't forget breaking changes - Mark with ! or footer
Don't ignore CI - Validate commits in pipeline

Install changelog-automation and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wshobson-agents-changelog-automation", "kind": "skill", "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.", "publisher": "wshobson", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/wshobson/agents", "path": "plugins/documentation-generation/skills/changelog-automation/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/wshobson/agents/changelog-automation", "key": "wshobson/agents/plugins/documentation-generation/skills/changelog-automation/SKILL.md" } }, "instructions": "# Changelog Automation\n\nPatterns and tools for automating changelog generation, release notes, and version management following industry standards.\n\n## When to Use This Skill\n\n- Setting up automated changelog generation\n- Implementing Conventional Commits\n- Creating release note workflows\n- Standardizing commit message formats\n- Generating GitHub/GitLab release notes\n- Managing semantic versioning\n\n## Core Concepts\n\n### 1. Keep a Changelog Format\n\n```markdown\n# Changelog\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://kee", "cost": { "context_tokens": 773 } }

changelog-automation

About