- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add tobihagemann/turbo --skill create-changelog -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add tobihagemann/turbo --skill create-changelog -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add tobihagemann/turbo --skill create-changelog -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add tobihagemann/turbo --skill create-changelog -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/tobihagemann/turbo/tree/HEAD/claude/skills/create-changelogDel publicador
Create a changelog backfilled with version history.
/changelog-rules SkillRun the /changelog-rules skill to load shared changelog conventions.
Use git rev-parse --show-toplevel to find the repository root. Look for the changelog file per /changelog-rules. If it already exists, use AskUserQuestion to confirm overwriting it. If the user declines (chooses the free-form "Other" option or asks to abort), stop without running the remaining steps.
Collect release history from the most authoritative source available:
gh release list --limit 100 --json tagName,name,publishedAt to list releases. For each release, read its notes with gh release view <tag> --json body --jq .body and parse them into changelog entries.git tag --sort=-v:refname to list tags. For each consecutive tag pair, run git log <older-tag>..<newer-tag> --oneline to collect commit summaries.For each version, classify entries into the standard change types and apply the changelog-worthiness criteria per /changelog-rules.
Write the changelog following the /changelog-rules file structure and conventions.
Briefly summarize how many versions were backfilled and which source was used (GitHub releases or git tags).
Create a keepachangelog CHANGELOG.md backfilled from GitHub releases or git tags. Use when the user asks to \"create a changelog\", \"add a changelog\", \"set up changelog\", or \"backfill changelog\"
---name: create-changelogdescription: Create a keepachangelog CHANGELOG.md backfilled from GitHub releases or git tags. Use when the user asks to…---# claude/skills/create-changelog/SKILL.mdResumen general
Create a keepachangelog CHANGELOG.md backfilled from GitHub releases or git tags. Use when the user asks to \"create a changelog\", \"add a changelog\", \"set up changelog\", or \"backfill changelog\".
Preguntas frecuentes
Descarga claude/skills/create-changelog/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/tobihagemann/turbo.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.