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

Add Changelog

by gambitph in gambitph/Stackable

Adds or updates a WordPress plugin changelog entry in readme.txt from the project's Release Roadmap for a confirmed plugin version.

GPL-3.0Auto-check passedDevelopment

Install Add Changelog

skills CLI
$ npx skills add gambitph/Stackable --skill add-changelog -a claude-code

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

GitHub CLI
$ gh skill install gambitph/Stackable add-changelog --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/gambitph/Stackable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/add-changelog .claude/skills/add-changelog && 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
add-changelog
GitHub stars
351
Token cost
~1.5k tokens
SKILL.md length
703 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
GPL-3.0

At a glance

Adds or updates a WordPress plugin changelog entry in readme.txt from the project's Release Roadmap for a confirmed plugin version.

  • Works in 6 steps: Resolve proposed version → Confirm version with user (required) → Detect new vs existing section → …
  • The user asks to add a changelog
  • SKILL.md covers Project context (do not…, Workflow and Quality checklist
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Add Changelog is an agent skill from gambitph/Stackable. Adds or updates a WordPress plugin changelog entry in readme.txt from the project's Release Roadmap for a confirmed plugin version. Use when the user asks to add a changelog, write changelog entries, update readme.txt Changelog, or invokes add-changelog.

Its SKILL.md is about 1.5k 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 Technical documentation. It works with WordPress, PHP and GitHub. The repository describes itself as: Page Builder Blocks for WordPress. An Amazing Block Library for the new WordPress Block Editor (Gutenberg). The licence is GPL-3.0.

When your agent uses it

  • The user asks to add a changelog
  • Write changelog entries
  • Update readme.txt Changelog
  • Invokes add-changelog

Example prompts

  • “/add-changelog”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Resolve proposed version
  2. Confirm version with user (required)
  3. Detect new vs existing section
  4. Collect Release Roadmap items
  5. Draft entries
  6. Write readme.txt

What it can do on your machine

Read from SKILL.md and the folder at commit 5c13d80. 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

Add Changelog loads about 1.5k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 703 words of instructions outside code blocks.

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

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 gambitph/Stackable at commit 5c13d80, republished under its GPL-3.0 licence (© gambitph). 703 words, ~1,476 tokens.

Download SKILL.mdSave it as .claude/skills/add-changelog/SKILL.md (or your agent's skills folder).
name
add-changelog
description
Adds or updates a WordPress plugin changelog entry in readme.txt from the project's Release Roadmap for a confirmed plugin version. Use when the user asks to add a changelog, write changelog entries, update readme.txt Changelog, or invokes add-changelog.
disable-model-invocation
true

Add Changelog

Add or update a == Changelog == entry in readme.txt for a confirmed plugin version, using issues and PRs from the project's Release Roadmap.

Project context (do not hardcode)

Do not embed repo URLs, org names, or project board links in this skill's workflow output or assumptions.

Instead, read the current project's Cursor rules (e.g. .cursor/rules/, especially anything covering repos, release roadmap, or project boards). Those rules are the source of truth for:

  • Main plugin repo(s)
  • Premium / companion repos (if any)
  • Release Roadmap / GitHub project board URL and how versions are organized

If those rules are missing or unclear, ask the user before guessing.

Workflow

Copy and track:

Add Changelog:
- [ ] 1. Resolve proposed version
- [ ] 2. Confirm version with user (wait for reply / override)
- [ ] 3. Detect new vs existing changelog section
- [ ] 4. Locate Release Roadmap items for that version
- [ ] 5. Draft concise changelog lines
- [ ] 6. Write into readme.txt (insert new or update existing)
1. Resolve proposed version

Find the plugin version from the WordPress plugin header Version: field:

  1. Prefer plugin.php in the project root.
  2. Else {plugin-slug}.php / {ProjectName}.php (main plugin bootstrap file).
  3. Optionally note Stable tag: in readme.txt for context; the plugin header Version is the default proposal.
2. Confirm version with user (required)

Stop and ask before collecting roadmap items or editing files.

Tell the user the proposed version (e.g. Found Version: 3.20.0 in plugin.php). Ask them to:

  • Confirm it, or
  • Type a different version number to use instead

Do not proceed until they reply. Use their confirmed (or overridden) value as VERSION.

3. Detect new vs existing section

In readme.txt, under == Changelog ==, check for a heading = VERSION =.

ResultMode
Heading missingNew — create a new section for VERSION
Heading presentUpdate — refresh that section from the Release Roadmap

Tell the user which mode you are using.

4. Collect Release Roadmap items

From the project's Cursor rules, open the Release Roadmap (GitHub project / issues list organized by target version).

Collect issues and PRs targeted at the same version as VERSION (matching the board's version field, column, or label — use whatever the project rules describe).

Prefer gh for GitHub access. Include:

  • Closed and open items still listed under that version (unless the user says closed-only)
  • Both issues and pull requests
  • Linked PR numbers when the fix lives on a PR; otherwise the issue number

Skip items that are clearly not user-facing (pure chores, triage-only, duplicate closes) unless the user wants everything.

5. Draft entries

Write concise, short, easy-to-understand lines for end users. Prefer area + outcome over implementation detail.

Format:

= VERSION =

* New: A new feature introduced #PR/Issue-number
* Change: Just a change that's either a new feature or a bug fix #PR/issue-number
* Fixed: Area fixed - short description of what was fixed #PR/issue-number
* More entries...

Prefixes:

PrefixUse for
New:New feature or capability
Change:Behavior/UX/API change that is not purely a bug fix
Fixed:Bug fix

Style rules:

  • One line per item; keep under ~100 characters when practical
  • Lead with the area when helpful (Image box - …, Posts block - …)
  • End with # + issue or PR number (no URL)
  • Prefer the PR number when a PR closed the work; else the issue number
  • Group loosely: New → Change → Fixed (optional but preferred)
  • No marketing fluff; no internal jargon

Example:

* Fixed: Image box - button group overlaps with each other #3300
Show full SKILL.md (246 more words)Show less
New mode

Draft a full new = VERSION = block from the Release Roadmap.

Update mode
  1. Read the existing bullets under = VERSION =.
  2. Rebuild the section from the Release Roadmap so it reflects current roadmap items.
  3. Keep existing lines that still match a roadmap item (same #number); rewrite wording only when the roadmap/title is clearer.
  4. Add missing roadmap items.
  5. Remove or replace bullets whose #number is no longer on the roadmap for this version (unless the user asks to keep orphans).
  6. Avoid duplicate #numbers.
6. Write readme.txt

After drafting, write immediately — no draft sign-off.

New mode

  1. Find == Changelog ==.
  2. Insert the new = VERSION = block immediately after that heading (above older versions).
  3. Preserve existing older changelog sections unchanged.

Update mode

  1. Replace the contents of the existing = VERSION = section (heading through the last bullet before the next = … = or end of changelog) with the draft.
  2. Do not create a second section for the same version.
  3. Leave all other version sections unchanged.

Match surrounding blank-line style (typically one blank line after = VERSION =, then bullets).

Briefly summarize what was written. Do not commit unless the user asks.

Quality checklist

  • Version confirmed (or overridden) by the user
  • Correct mode: new insert vs update existing section
  • Items come from the Release Roadmap for that version (via project Cursor rules)
  • Lines use New: / Change: / Fixed: and end with #number
  • Wording is user-facing and brief
  • New sections go at the top of Changelog; updates stay in place

© gambitph, GPL-3.0. 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 .cursor/skills/add-changelog of gambitph/Stackable.

Open the folder on GitHubat commit 5c13d80

Compare with similar skills

Add Changelog 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.

Add Changelog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Changelog this skillgambitph/Stackable351—~1.5kAutomated safety check: PassGPL-3.0
Changelogduracelltomi/gtm4wp174—~2.2kAutomated safety check: PassGPL-2.0-or-later
Ccb GitHubSeemSeam/claude_codex_bridge3.6k—~4.9kAutomated safety check: PassCustom licence
Make Releaseatgreen/cl-tuition149—~1.3kAutomated safety check: PassMIT
Releasesol4k/sol4k135—~949Automated safety check: PassApache-2.0
Verify Releaseillegalstudio/elephc608—~2.5kAutomated safety check: PassMIT

Similar skills

  • Changelog

    duracelltomi/gtm4wp

    How to write GTM4WP CHANGELOG.md / readme.txt entries. An agent skill from duracelltomi/gtm4wp.

    174 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Ccb GitHub

    SeemSeam/claude_codex_bridge

    Maintain this CCB project's GitHub-facing release and npm publication surface.

    3.6k GitHub stars~4.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Make Release

    atgreen/cl-tuition

    Cut a new tuition release — verify release notes, tuition.asd version, README currency, a clean tree, and a green test suite, then tag vX.Y.Z and push so CI builds the GitHub release.

    149 GitHub stars~1.3k tokensUpdated 26 days ago
    DevelopmentAuto-check passed

  • Release

    sol4k/sol4k

    Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.

    135 GitHub stars~949 tokensUpdated 11 days ago
    DevelopmentAuto-check passed

  • Verify Release

    illegalstudio/elephc

    Pre-release verification that first requires a complete release-changelog audit, then checks README, docs, roadmap, test coverage, examples, and the full test suite for regressions.

    608 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Release

    emanuelcasco/pi-mono-extensions

    Release a new version of pi-extensions: bump individual package versions (independent mode), update CHANGELOGs and READMEs, create per-package git tags, publish a GitHub release, and publish…

    106 GitHub stars~2.3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from gambitph/Stackable

All 18 skills in this repo

  • Wp Block Development

    gambitph/Stackable

    A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…

    351 GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed

  • Wp Block Themes

    gambitph/Stackable

    A skill your agent uses when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style…

    351 GitHub starsUsed in 3 repos~985 tokens
    Auto-check passed

  • Wp Performance

    gambitph/Stackable

    A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…

    351 GitHub starsUsed in 3 repos~1.5k tokens
    Auto-check passed

  • Wp Plugin Development

    gambitph/Stackable

    A skill your agent uses when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security…

    351 GitHub starsUsed in 3 repos~999 tokens
    Auto-check passed

  • Wp Project Triage

    gambitph/Stackable

    A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…

    351 GitHub starsUsed in 3 repos~371 tokens
    Auto-check passed

  • Wp Plugin Directory Guidelines

    gambitph/Stackable

    A skill your agent uses when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or…

    351 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Works with

Categories

Questions about Add Changelog

What does Add Changelog do?

Adds or updates a WordPress plugin changelog entry in readme.txt from the project's Release Roadmap for a confirmed plugin version. Add Changelog is an agent skill from gambitph/Stackable.txt from the project's Release Roadmap for a confirmed plugin version.

When should I use Add Changelog?

Add Changelog fits situations like: the user asks to add a changelog; write changelog entries; update readme.txt Changelog; invokes add-changelog.

How do I install Add Changelog in Claude Code?

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

How do I install Add Changelog in Codex?

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

Can I use Add Changelog 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 gambitph/Stackable --skill add-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-changelog, .gemini/skills/add-changelog, .github/skills/add-changelog and .opencode/skills/add-changelog in your project.

What does Add Changelog need to run?

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

Does Add Changelog 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 Add Changelog 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 Add Changelog use?

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

How many tokens does Add Changelog use?

About 1.5k tokens (SKILL.md is roughly 5.9k 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 Add Changelog?

Skills that share tags, products or a category with Add Changelog: Changelog (duracelltomi/gtm4wp, 174 stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars), Make Release (atgreen/cl-tuition, 149 stars) and Release (sol4k/sol4k, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Changelog?

gambitph (a GitHub organization) maintains it in gambitph/Stackable, which has 351 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

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