Skip to content

rse/ase / plugin/skills/ase-repo-changelog

ase-repo-changelog

Verified

Update ChangeLog entries in CHANGELOG.md files, optionally just for the staged and/or unstaged changes, in the own ASE format or in foreign formats like Keep a Changelog. Use when the user wants to "add a changelog entry", or to "update", "complete", or "consolidate" the "changelog", "ChangeLog", or "CHANGELOG.md", e.g. before committing or releasing.

FileKindSize
SKILL.mdskill md14.3 KB
help.mdmarkdown5.0 KB

##  NAME

`ase-repo-changelog` - Update ChangeLog Entries

##  SYNOPSIS

`ase-repo-changelog`
    [`--help`|`-h`]
    [`--staged`|`-s`]
    [`--unstaged`|`-u`]
    [`--file`|`-f` *path*]
    [`--format`|`-F` `AUTO`|`RSE`|`KAC`|`CCL`]

##  DESCRIPTION

The `ase-repo-changelog` skill helps to *complete*, *consolidate*, and
*sort* the entries of the most recent section of a `CHANGELOG.md`
file, based on the underlying *Git* commits and the currently staged
changes in the Git *index*.

By default, the skill operates on the nearest `CHANGELOG.md` file in
the current directory or one of its parent directories. With `--file`,
it operates on an explicitly given file instead, e.g. on the
`CHANGELOG.md` of a sub-project in a monorepo.

With `--staged` and/or `--unstaged`, the skill instead creates entries
just for the current, *uncommitted* change set: it skips the scan of
the Git commits since the last tag and leaves all other entries of the
section unchanged. This is cheap and fast for the usual "stage →
changelog → commit" flow.

If the most recent section is already released, i.e., a Git tag
`N.M.K` (or `vN.M.K`) of its version exists, it is left untouched and
a new section for the next patch version is inserted above it instead,
which then receives the new entries.

The skill knows the following *ChangeLog formats*, guesses the format
of the file from its content, and writes the entries in its vocabulary:

-   `RSE`: the own format of *ASE*, where each entry starts with
    `<change-type> [<artifact-kind>]: <summary>`, *change-type* is one of
    `FEATURE`, `IMPROVEMENT`, `BUGFIX`, `UPDATE`, `CLEANUP`, or
    `REFACTOR`, and *artifact-kind* is one or more comma-separated
    *artifact class* tags out of `spec`, `code`, `docs`, `infr`, or
    `othr`. Entries are grouped and sorted by this prefix.

-   `KAC`: *Keep a Changelog*, where the entries are collected in a
    `## [Unreleased]` section, below the headers `### Added`,
    `### Changed`, `### Deprecated`, `### Removed`, `### Fixed`, and
    `### Security`.

-   `CCL`: *Conventional Changelog*, where the entries are placed below
    headers like `### Features` and `### Bug Fixes`.

An empty file gets the `RSE` format, while the style of a file in an
unrecognized format is mimicked. The date in a dated section header is
also updated to the current date.

The layout of the entries follows the style of the existing entries
of the file (e.g. a single line, a title line plus an explaining body,
or a wrapped sentence), and each entry is kept within about 5 lines.

The updated `CHANGELOG.md` is left *unstaged*, as it may carry further
unrelated changes. Stage the new entry yourself (e.g. via `git add -p`),
or use `ase-repo-stage --changelog` to update and stage it together
with a selection of changes.

##  OPTIONS

-   `--staged`|`-s`:
    Create entries just for the *staged* changes in the Git *index*,
    instead of for the Git commits since the last tag plus the staged
    changes. Combined with `--unstaged`, create entries for *all*
    uncommitted changes.

-   `--unstaged`|`-u`:
    Create entries just for the *unstaged* changes and the *untracked*
    files of the working copy (except *ASE*'s own state below `.ase/`),
    instead of for the Git commits since the last tag plus the staged
    changes. Combined with `--staged`, create entries for *all*
    uncommitted changes.

-   `--file`|`-f` *path*:
    Operate on the given *ChangeLog* file *path* (relative to the
    current directory) instead of the nearest `CHANGELOG.md` in the
    current directory or one of its parent directories, e.g. on the
    `CHANGELOG.md` of a sub-project like `tool/` or `pages/` in a
    monorepo.

-   `--format`|`-F` `AUTO`|`RSE`|`KAC`|`CCL`:
    Use the given *ChangeLog* format instead of guessing it from the
    file content (`AUTO`, the default), e.g. to start an empty
    `CHANGELOG.md` of a foreign repository in the *Keep a Changelog*
    format `KAC`.

##  SCENARIOS

-   You want the `CHANGELOG.md` brought up to date with recent commits
-   You want changelog entries completed, consolidated, and sorted
-   You want a tidy changelog section before a release
-   You want an entry just for the staged changes before committing them
-   You want the changelog of a particular sub-project of a monorepo updated
-   You want the changelog of a foreign repository updated in its own format

##  EXAMPLES

Update the most recent ChangeLog section:

```text
❯ /ase-repo-changelog
```

Create entries just for the staged changes:

```text
❯ /ase-repo-changelog --staged
```

Create entries for all uncommitted changes:

```text
❯ /ase-repo-changelog -s -u
```

Create entries for the staged changes in the ChangeLog of a sub-project:

```text
❯ /ase-repo-changelog --staged --file tool/CHANGELOG.md
```

Create entries in the *Keep a Changelog* format:

```text
❯ /ase-repo-changelog --format KAC
```

##  SEE ALSO

[`ase-repo-commit`](../ase-repo-commit/help.md), [`ase-repo-stage`](../ase-repo-stage/help.md), [`ase-docs-proofread`](../ase-docs-proofread/help.md).
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall