Saltar al contenido
TakoAPI
Volver a skills

git-changelog

por fratua

Git & GitHub
581Descargas según clawskills.sh
0Vistas
0 me gustaInicia sesión para dar me gusta a esta skill
—Aún sin valoraciones
Tu valoración

Resumen

Auto-generate beautiful changelogs from git history, grouped by conventional commit types.

Descripción

Qué hace esta skill

Reads git commit history and produces a categorized, markdown-formatted changelog grouped by conventional commit types. Handles tag ranges, date ranges, and breaking change detection automatically. Output is ready to paste into CHANGELOG.md or a GitHub release.

Parsing conventional commits and grouping them by type by hand is tedious and error-prone, especially across long ranges; this skill automates the whole process in one step.

Cuándo usarla

  • Generating release notes before tagging a new version
  • Creating a CHANGELOG.md entry after a sprint
  • Reviewing what changed between two git tags
  • Catching breaking changes before publishing a package
  • Summarizing recent commits for a team update

Flujo de trabajo de ejemplo

ENTRADA

User asks: generate a changelog from v1.1.0 to HEAD

AGENTE
  1. 1

    Verify the current directory is a git repository using git rev-parse

  2. 2

    Determine the commit range from v1.1.0 to HEAD

  3. 3

    Extract commits with hash, subject, author, and date using git log

  4. 4

    Parse each commit subject for conventional commit prefixes and group into categories

  5. 5

    Check for BREAKING CHANGE footers and feat! commits, then render the full markdown output

SALIDA

A markdown changelog with sections for Features, Bug Fixes, and any other detected categories, including short commit hashes and scopes

Instalación

clawhub install fratua/git-changelog

Ejecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.

Enlaces