New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Changelog Generator

by brunosabot in brunosabot/streamline-card

Generate an engaging, human-centric, and community-focused changelog from git history.

MITAuto-check passedDevelopment

Install Changelog Generator

skills CLI
$ npx skills add brunosabot/streamline-card --skill changelog-generator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brunosabot/streamline-card changelog-generator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brunosabot/streamline-card.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/changelog-generator .claude/skills/changelog-generator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
changelog-generator
GitHub stars
269
Token cost
~854 tokens
SKILL.md length
440 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Generate an engaging, human-centric, and community-focused changelog from git history.

  • Works in 5 steps: Analyze History: Read commits since the… → Identify Themes: Group changes into "🚀… → Ask for Context: Ask the user for the… → …
  • This when the user asks for whats new
  • SKILL.md covers Tone & Personality, Steps, Output Structure and Formatting Guidelines
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Changelog Generator is an agent skill from brunosabot/streamline-card. Generate an engaging, human-centric, and community-focused changelog from git history. Trigger this when the user asks for "what's new", "release notes", or "changelog". Inspired by the polished yet passionate styles of Streamline Card and Bubble Card.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Git workflow. It works with Home Assistant. The repository describes itself as: Streamline your Lovelace configuration with with a card template system. The licence is MIT.

When your agent uses it

  • This when the user asks for whats new
  • Tasks that involve Changelog and release notes
  • Tasks that involve Git workflow

Example prompts

  • “release notes”
  • “changelog”
  • “/changelog-generator”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Analyze History: Read commits since the latest tag or between specific tags.
  2. Identify Themes: Group changes into "🚀 What's New for You" and "🔧 Technical Polish & Stability".
  3. Ask for Context: Ask the user for the "story" behind the release to include in the intro.
  4. Credit Contributors: Identify all contributors mentioned in PRs or commit messages. Exclude the project owner/maintainer (the user) from…
  5. Draft the Narrative: Write a two-paragraph intro that is sincere and incorporates the exact user context.

What it can do on your machine

Read from SKILL.md and the folder at commit 3a2667f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Changelog Generator loads about 854 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 440 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~854

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brunosabot/streamline-card at commit 3a2667f, republished under its MIT licence (© brunosabot). 440 words, ~854 tokens.

Download SKILL.mdSave it as .claude/skills/changelog-generator/SKILL.md (or your agent's skills folder).
name
changelog-generator
description
Generate an engaging, human-centric, and community-focused changelog from git history. Trigger this when the user asks for "what's new", "release notes", or "changelog". Inspired by the polished yet passionate styles of Streamline Card and Bubble Card.

Changelog Generator

Your goal is to transform a cold list of git commits into a warm, narrative-driven update. It must feel like a sincere letter from a developer who is passionate about their work.

Tone & Personality

  • Sincere & Grounded: Avoid kitschy or "customer service" greetings. Be direct and sincere about the project.
  • Strictly Factual Context: You MUST ask the user for personal context before finalizing the intro. Use their answer to make the intro more human. DO NOT hallucinate or assume things. Stick to the facts they provide.
  • Contextual Emojis: Emojis must match the content of the change (e.g., 🔢 or ⚖️ for booleans, ⚡ for performance, 🎨 for UI).

Steps

  1. Analyze History: Read commits since the latest tag or between specific tags.
  2. Identify Themes: Group changes into "🚀 What's New for You" and "🔧 Technical Polish & Stability".
  3. Ask for Context: Ask the user for the "story" behind the release to include in the intro.
  4. Credit Contributors: Identify all contributors mentioned in PRs or commit messages. Exclude the project owner/maintainer (the user) from this list.
  5. Draft the Narrative: Write a two-paragraph intro that is sincere and incorporates the exact user context.

Output Structure

  1. Greeting: Always start with exactly: "Hello there!"
  2. The Personal Update:
    • Paragraph 1: A sincere opening incorporating the exact context provided by the user. Keep details fatuals.
    • Paragraph 2: A summary of what this specific release aims to achieve.
  3. 🚀 What's New for You:
    • Use bullet points for features.
    • EMOJI PLACEMENT IS CRITICAL: The emoji MUST be placed at the very beginning of the bullet point, immediately after the dash. Example: - 🎨 **New UI**: ...
    • Use a diverse range of emojis that specifically represent the nature of the change.
  4. 🔧 Technical Polish & Stability:
    • MUST BE A CONCISE LIST: Use a bulleted list for these items.
    • SHORTER THAN FEATURES: This section MUST be noticeably shorter and less detailed than the "What's New for You" section.
    • Ruthlessly combine similar technical tasks into brief summaries. Do not provide paragraphs of technical detail.
    • No individual emojis for bullet points in this section.
    • Briefly explain why the work matters to a human.
  5. ❤️ Huge Thanks:
    • Contributor Recognition: Write a dedicated paragraph per contributor.
    • Exclude the Maintainer: NEVER include the project owner/maintainer in the thanks credits.
    • Bold Contributors: Bold all contributor names (e.g., "@user").
    • Mention specifically what they helped with to make it personal.
Show full SKILL.md (52 more words)Show less

Formatting Guidelines

  • Intro Layout: Blank line after the greeting and between intro paragraphs.
  • Emoji Consistency:
    • User Features: Diverse range of content-matching emojis placed AT THE VERY BEGINNING of the line.
    • Technical: No emojis for bullet points. Keep it strictly shorter than the User Features section.
    • Section Headers: 🚀 for User Features, 🔧 for Tech.

© brunosabot, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/changelog-generator of brunosabot/streamline-card.

Open the folder on GitHubat commit 3a2667f

Compare with similar skills

Changelog Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Changelog Generator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changelog Generator this skillbrunosabot/streamline-card269—~854Automated safety check: PassMIT
Releasedcb/homeassistant-claude-kit123—~3.1kAutomated safety check: PassMIT
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills105k2 repos~3.5kAutomated safety check: NotesMIT
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause
Hunk Release Workflowmodem-dev/hunk9.6k—~3.8kAutomated safety check: PassMIT

Similar skills

  • Release

    dcb/homeassistant-claude-kit

    Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.

    123 GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    105k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • Go-Redis Release Preparation

    redis/go-redis

    Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Hunk Release Workflow

    modem-dev/hunk

    Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.

    9.6k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • pybind11 Release Preparation

    pybind/pybind11

    Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.

    18k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from brunosabot/streamline-card

  • Issue To Regression Test

    brunosabot/streamline-card

    A skill your agent uses when the user asks to fix a bug, references a GitHub issue number, or describes an issue and wants a fix.

    269 GitHub stars~529 tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Changelog Generator

What does Changelog Generator do?

Generate an engaging, human-centric, and community-focused changelog from git history. Changelog Generator is an agent skill from brunosabot/streamline-card. Generate an engaging, human-centric, and community-focused changelog from git history.

When should I use Changelog Generator?

Changelog Generator fits situations like: this when the user asks for whats new; tasks that involve Changelog and release notes; tasks that involve Git workflow.

How do I install Changelog Generator in Claude Code?

Run `npx skills add brunosabot/streamline-card --skill changelog-generator -a claude-code`. Or copy the skill folder (.agents/skills/changelog-generator in brunosabot/streamline-card) into .claude/skills/changelog-generator in your project. Claude Code loads it when a task matches its description.

How do I install Changelog Generator in Codex?

Run `npx skills add brunosabot/streamline-card --skill changelog-generator -a codex`. Or copy the skill folder (.agents/skills/changelog-generator in brunosabot/streamline-card) into .agents/skills/changelog-generator in your project. Codex loads it when a task matches its description.

Can I use Changelog Generator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brunosabot/streamline-card --skill changelog-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changelog-generator, .gemini/skills/changelog-generator, .github/skills/changelog-generator and .opencode/skills/changelog-generator in your project.

What does Changelog Generator need to run?

SKILL.md names no scripts, command-line tools or credentials: Changelog Generator is instructions for the agent only.

Does Changelog Generator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Changelog Generator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Changelog Generator use?

Changelog Generator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Changelog Generator use?

About 854 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Changelog Generator?

Skills that share tags, products or a category with Changelog Generator: Release (dcb/homeassistant-claude-kit, 123 stars), Release Bump (jamiepine/voicebox, 57k stars), Git Workflow and Versioning (addyosmani/agent-skills, 105k stars) and Go-Redis Release Preparation (redis/go-redis, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changelog Generator?

brunosabot (a GitHub user) maintains it in brunosabot/streamline-card, which has 269 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on May 24, 2026.

Source: brunosabot/streamline-card on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.