git-release

Parse git logs, categorize commits, and draft release notes with version bumps.

1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill git-release-hadenlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/git-release
Command: npx skills add https://github.com/hadenlabs/tasks --skill git-release-hadenlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft release notes from merged PRs and propose a version bump to streamline software releases and improve stakeholder communication.

Core Features & Use Cases

  • Draft release notes from merged PRs
  • Propose a semantic version bump
  • Provide a copy-pasteable glab release command
  • Use Case: generate release notes for a feature release after multiple PRs are merged to accompany a tagged release.

Quick Start

Prepare a release draft by summarizing the latest merged PRs and propose a version bump.

Frequently Asked Questions about git-release

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

FAQPage Schema
How do I generate release notes from merged PRs automatically?

To generate release notes from merged PRs, you need a tool that parses git logs and categorizes commits. This Skill drafts release notes by summarizing merged pull requests and proposing a semantic version bump for your software project.

How do I determine the correct semantic version bump for a new release?

To determine the correct semantic version bump, the workflow analyzes your git history and categorizes merged PRs. It evaluates the commit categories to propose the appropriate version increment for your tagged release.

Can I automate changelog generation for GitLab releases using glab?

Yes, you can automate changelog generation for GitLab releases. This workflow produces a ready-to-run glab release command alongside your drafted changelog, allowing you to execute the release directly from your terminal.

What is the best way to draft a changelog from git history for stakeholders?

The best way to draft a changelog from git history is to parse commit logs and categorize merged PRs. This approach creates a consistent changelog draft suitable for sharing with stakeholders alongside a semantic version release.

Does this release drafting workflow require a specific branching strategy?

No specific branching strategy is required, but the workflow is suitable for software projects with Git history. It relies on parsing merged PRs to generate release notes and version bumps, assuming releases follow semantic versioning.

Why are my git commit messages not categorized correctly in the changelog?

Git commit messages may not be categorized correctly if they lack clear PR context. The workflow parses git logs and categorizes merged PRs to generate the changelog, so unstructured commit messages might affect the output quality.