omcustom-release-notes

Generate markdown release notes from git history and closed issues.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill omcustom-release-notes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omcustom-release-notes
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/omcustom-release-notes
Command: npx skills add https://github.com/baekenough/second-brain --skill omcustom-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate structured release notes directly from git history and closed issues within Claude Code sessions, replacing CI-based workflows.

Core Features & Use Cases

  • In-session release notes generation from commits and closed issues for a given version.
  • Classification of changes into Features, Bug fixes, Docs, and other categories for clear stakeholder communication.
  • Output ready-to-use notes for GitHub releases or internal docs, with a repeatable, auditable trace of changes.

Quick Start

Run /omcustom-release-notes <version> [--previous-tag <tag>] to generate release notes from the repository history.

Frequently Asked Questions about omcustom-release-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes from git history automatically?

Generate release notes from git history automatically by running the Skill with a target version. It parses local git tags, commits, and closed issues to classify changes into Features, Bug fixes, and Docs for a markdown-ready output.

Can I generate GitHub release notes from closed issues and commits in Claude Code?

Yes, you can generate GitHub release notes from closed issues and commits directly within Claude Code. The tool integrates local git metadata to classify changes and produce a markdown-ready body suitable for gh release commands.

How do I categorize commits into features and bug fixes for a software release?

Categorize commits into features and bug fixes by analyzing git history and closed issue metadata. The Skill automatically classifies changes into distinct sections like Features, Bug fixes, and Docs to ensure clear stakeholder communication.

What is the best way to replace CI-based release notes generation with an in-session workflow?

Replace CI-based release notes generation by running the Skill in-session to extract git history and closed issues. It uses local tags to assemble categorized markdown notes, providing a repeatable and auditable trace of changes without CI dependencies.

Do I need a previous git tag to generate release notes for a specific version?

You do not strictly need a previous git tag, but providing one via the --previous-tag flag helps scope the release notes accurately. The Skill defaults to using available local git tags to determine the commit range for the specified version.