How do I install the Chloggen skill?

Run npx skillmds@latest add newrelic/chloggen in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Chloggen safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Chloggen?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Chloggen free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Chloggen?

newrelic (@newrelic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Chloggen by newrelic — Agent Skill

Name: Chloggen
Author: newrelic

Chloggen

Use when adding a changelog entry to this repo — creating or editing files in `.chloggen/`, running `make chlog-new/-validate/-preview/-update`, or preparing a user-facing PR whose release notes should show up in CHANGELOG.md. Covers the draft-PR-first dance that lets `make chlog-new` auto-fill the PR number and change type.

newrelic 09f3db1 2 files · 4.8 KB Updated Sep 17, 2026

File contents

chloggen Workflow

This repo uses chloggen to generate CHANGELOG.md from per-PR YAML entries in .chloggen/. Every user-facing PR needs one entry.

Commands

make chlog-new — create a template entry named after the current branch, auto-filling issues: and change_type if a PR already exists.
make chlog-validate — validate all pending entries. Fails if any entry has empty issues:.
make chlog-preview — dry-run the CHANGELOG update.
make chlog-update — consume entries and write to CHANGELOG.md (release only).

Change types allowed here: feature, bug_fix, docs. The wrapper in scripts/chloggen-wrapper.sh translates these to chloggen's built-ins — don't hand-edit it.

Preferred workflow (draft PR first)

make chlog-new reads the PR for the current branch to prefill issues: and infer change_type from the PR title's conventional-commit prefix (feat → feature, fix → bug_fix, docs → docs). To use that, create the PR as a draft first so nothing publishes before the entry lands.

Make code changes on your branch, commit, push.
gh pr create --draft --title "feat: ..." --body "..."
make chlog-new — writes .chloggen/<branch>.yaml with issues: [N] and change_type prefilled.
Edit the file: fill in note: (one-line description). Add subtext: only if extra detail is warranted.
make chlog-validate — should pass now.
Commit the entry, push.
gh pr ready <PR> — promote out of draft.

If you already opened a non-draft PR

make chlog-new still works; run it and it will fill in the PR number. Or hand-edit the template and set issues: [N] yourself. Commit as a follow-up.

Gotchas

chlog-validate errors with specify one or more issues #'s when issues: is empty — that means no PR existed when make chlog-new ran. Fill it in and re-run.
Entry filename is <branch-name>.yaml (slashes replaced with underscores). Don't rename it.
.chloggen/TEMPLATE.yaml and .chloggen/config.yaml are not entries; the wrapper skips them.

---name: chloggendescription: Use when adding a changelog entry to this repo — creating or editing files in `.chloggen/`, running `make chlog-new/-validate/-preview/-update`, or preparing a user-facing PR whose release notes should show up in CHANGELOG.md. Covers the draft-PR-first dance that lets `make chlog-new` auto-fill the PR number and change type.---# chloggen WorkflowThis repo uses chloggen to generate CHANGELOG.md from per-PR YAML entries in `.chloggen/`. Every user-facing PR needs one entry.## Commands- `make chlog-new` — create a template entry named after the current branch, auto-filling `issues:` and `change_type` if a PR already exists.- `make chlog-validate` — validate all pending entries. Fails if any entry has empty `issues:`.- `make chlog-preview` — dry-run the CHANGELOG update.- `make chlog-update` — consume entries and write to CHANGELOG.md (release only).Change types allowed here: `feature`, `bug_fix`, `docs`. The wrapper in `scripts/chloggen-wrapper.sh` translates these to chloggen's built-ins — don't hand-edit it.## Preferred workflow (draft PR first)`make chlog-new` reads the PR for the current branch to prefill `issues:` and infer `change_type` from the PR title's conventional-commit prefix (`feat` → feature, `fix` → bug_fix, `docs` → docs). To use that, create the PR as a draft first so nothing publishes before the entry lands.1. Make code changes on your branch, commit, push.2. `gh pr create --draft --title "feat: ..." --body "..."`3. `make chlog-new` — writes `.chloggen/<branch>.yaml` with `issues: [N]` and `change_type` prefilled.4. Edit the file: fill in `note:` (one-line description). Add `subtext:` only if extra detail is warranted.5. `make chlog-validate` — should pass now.6. Commit the entry, push.7. `gh pr ready <PR>` — promote out of draft.## If you already opened a non-draft PR`make chlog-new` still works; run it and it will fill in the PR number. Or hand-edit the template and set `issues: [N]` yourself. Commit as a follow-up.## Gotchas- `chlog-validate` errors with `specify one or more issues #'s` when `issues:` is empty — that means no PR existed when `make chlog-new` ran. Fill it in and re-run.- Entry filename is `<branch-name>.yaml` (slashes replaced with underscores). Don't rename it.- `.chloggen/TEMPLATE.yaml` and `.chloggen/config.yaml` are not entries; the wrapper skips them.

Frequently asked questions