release-description

Generate a one-line release description from commits since the latest tag.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bitsocialnet/bitsocial-web --skill release-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-description
Source: https://github.com/bitsocialnet/bitsocial-web/tree/main/.codex/skills/release-description
Command: npx skills add https://github.com/bitsocialnet/bitsocial-web --skill release-description

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the creation of a concise one-line release description from commit titles since the last git tag, reducing manual effort in preparing release notes.

Core Features & Use Cases

  • Analyze commits since the latest tag and categorize changes by Conventional Commits prefixes (feat:, fix:, perf:, refactor:, chore:, docs:).
  • Update the oneLinerDescription constant in scripts/release-body.js with a clear, high-level summary suitable for release notes.
  • Use when preparing release notes one-liners or release bodies for new versions, ensuring consistency across versions.

Quick Start

Update the one-liner release description by analyzing commits since the latest tag and writing the result to scripts/release-body.js.

Frequently Asked Questions about release-description

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

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

To generate release notes from git commit messages automatically, this Skill analyzes commit titles since the latest tag, categorizes them by Conventional Commits prefixes, and writes a concise one-line summary to scripts/release-body.js.

How do I create a one-line release description from Conventional Commits?

Creating a one-line release description from Conventional Commits involves parsing commit prefixes like feat: and fix: since the last tag, categorizing the changes, and updating the oneLinerDescription constant in your release-body.js script.

What is the best way to summarize git commits for a release body?

The best way to summarize git commits for a release body is to automate commit analysis from the latest tag, grouping changes by Conventional Commits prefixes to produce a high-level summary suitable for release notes.

Does this release notes generator require a specific file structure to write summaries?

Yes, this release notes generator requires a specific file structure, writing the generated one-line release summary directly into the oneLinerDescription constant within scripts/release-body.js.

What commit prefixes are categorized when generating release notes?

When generating release notes, the tool categorizes commit prefixes defined by the Conventional Commits standard, specifically parsing feat:, fix:, perf:, refactor:, chore:, and docs: tags from commit titles.