Skip to content

thatrebeccarae/claude-marketing / skills/release-notes

release-notes

Verified

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

FileKindSize
EXAMPLES.mdmarkdown4.9 KB
LICENSEother1.0 KB
REFERENCE.mdmarkdown4.3 KB
SKILL.mdskill md5.8 KB

EXAMPLES.md

View on GitHub
# release-notes — Examples

## Example 1: Generate changelog for a repo with conventional commits

**Input:**
```
/release-notes changelog
```

**Git history since last tag (v2.3.1):**
```
a1b2c3d feat(auth): add OAuth2 PKCE support (#112)
d4e5f6a fix(api): handle null response from upstream (#108)
f7a8b9c fix(ui): correct date picker timezone offset (#110)
c0d1e2f docs: update API authentication guide (#111)
3a4b5c6 chore: upgrade eslint to v9 (#109)
e7f8a9b feat!: remove deprecated /v1/users endpoint (#113)
```

**Generated changelog entry:**
```markdown
## [3.0.0] — 2026-03-19

### Breaking Changes
- Remove deprecated /v1/users endpoint (#113)

### Added
- Add OAuth2 PKCE support for auth flow (#112)

### Fixed
- Handle null response from upstream API (#108)
- Correct date picker timezone offset (#110)

### Documentation
- Update API authentication guide (#111)

### Maintenance
- Upgrade eslint to v9 (#109)
```

**Suggested version:** 3.0.0 (major bump due to breaking change). User confirms, entry is prepended to CHANGELOG.md.

---

## Example 2: Generate changelog for a repo without conventional commits

**Input:**
```
/release-notes changelog ~/projects/legacy-app
```

**Git history since last tag (v0.8.0):**
```
a1b2c3d Added dark mode toggle to settings page (#45)
d4e5f6a Fix crash when opening empty project (#41)
f7a8b9c Updated README with new screenshots
c0d1e2f Refactored database connection pooling
3a4b5c6 Bump dependencies
e7f8a9b Fixed typo in error message (#43)
```

**AI categorization (presented for review):**
```
Added:
  - "Added dark mode toggle" → Added (keyword: "Added")
Fixed:
  - "Fix crash when opening empty project" → Fixed (keyword: "Fix")
  - "Fixed typo in error message" → Fixed (keyword: "Fixed")
Changed:
  - "Refactored database connection pooling" → Changed (keyword: "Refactored")
Documentation:
  - "Updated README with new screenshots" → Documentation (keyword: "README")
Maintenance:
  - "Bump dependencies" → Maintenance (keyword: "Bump")
```

**Generated changelog entry:**
```markdown
## [0.9.0] — 2026-03-19

### Added
- Dark mode toggle in settings page (#45)

### Fixed
- Crash when opening empty project (#41)
- Typo in error message (#43)

### Changed
- Refactored database connection pooling

### Documentation
- Updated README with new screenshots

### Maintenance
- Bump dependencies
```

**Suggested version:** 0.9.0 (minor bump — new feature, no breaking changes).

---

## Example 3: Create a GitHub release with changelog entry

**Input:**
```
/release-notes release ~/projects/my-api v4.1.0
```

**Procedure:**
1. Commits collected and categorized (3 features, 2 fixes).
2. Changelog entry formatted and shown to user.
3. User approves.
4. Entry prepended to CHANGELOG.md.
5. GitHub release created:

```bash
gh release create v4.1.0 --title "v4.1.0" --notes "$(cat <<'EOF'
## What's New

### Added
- Batch endpoint for bulk operations (#201)
- Rate limiting with configurable thresholds (#198)
- Health check endpoint with dependency status (#195)

### Fixed
- Memory leak in WebSocket connection handler (#199)
- Incorrect pagination headers on empty results (#196)

**Full Changelog**: https://github.com/user/repo/compare/v4.0.0...v4.1.0
EOF
)"
```

Output: `https://github.com/user/repo/releases/tag/v4.1.0`

---

## Example 4: Retroactively generate changelog from full history

**Input:**
```
/release-notes init ~/projects/side-project
```

**Repo state:** 3 tags exist (`v0.1.0`, `v0.2.0`, `v1.0.0`), plus 8 untagged commits after `v1.0.0`.

**Procedure:**
1. Walk all tags in chronological order.
2. For each tag range, collect and categorize commits.
3. Generate entries for `v0.1.0`, `v0.2.0`, `v1.0.0`, and an `[Unreleased]` section.
4. Present the full CHANGELOG.md to the user for review.
5. On approval, write the file.

**Generated CHANGELOG.md:**
```markdown
# 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).

## [Unreleased]

### Added
- WebSocket support for real-time updates (#18)

### Fixed
- Connection timeout on slow networks (#17)

## [1.0.0] — 2026-01-15

### Breaking Changes
- New authentication required for all endpoints (#14)

### Added
- Full REST API (#12)
- User management (#13)

## [0.2.0] — 2025-11-20

### Added
- Database persistence (#8)
- Configuration file support (#7)

### Fixed
- Startup crash on missing env vars (#9)

## [0.1.0] — 2025-10-01

### Added
- Initial project setup
- Basic CLI interface (#1)
- Core processing engine (#2)

[Unreleased]: https://github.com/user/repo/compare/v1.0.0...HEAD
[1.0.0]: https://github.com/user/repo/compare/v0.2.0...v1.0.0
[0.2.0]: https://github.com/user/repo/compare/v0.1.0...v0.2.0
[0.1.0]: https://github.com/user/repo/releases/tag/v0.1.0
```

User reviews, requests moving one entry from Changed to Added, approves the corrected version, and the file is written.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall