Agent skill

Upgrade Changelog

Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go

Apache-2.0Auto-check passedDevelopment

Install Upgrade Changelog

skills CLI

$ npx skills add akash-network/node --skill upgrade-changelog -a claude-code

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

GitHub CLI

$ gh skill install akash-network/node upgrade-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/akash-network/node.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/upgrade-changelog .claude/skills/upgrade-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/

Paste into Claude Code

Install the "upgrade-changelog" agent skill from https://github.com/akash-network/node/tree/main/.agents/skills/upgrade-changelog into .claude/skills/upgrade-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-changelog", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/akash-network/node/tree/main/.agents/skills/upgrade-changelog

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add akash-network/node --skill upgrade-changelog -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install akash-network/node upgrade-changelog --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akash-network/node.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/upgrade-changelog .agents/skills/upgrade-changelog && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "upgrade-changelog" agent skill from https://github.com/akash-network/node/tree/main/.agents/skills/upgrade-changelog into .agents/skills/upgrade-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-changelog", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add akash-network/node --skill upgrade-changelog -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install akash-network/node upgrade-changelog --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akash-network/node.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/upgrade-changelog .cursor/skills/upgrade-changelog && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "upgrade-changelog" agent skill from https://github.com/akash-network/node/tree/main/.agents/skills/upgrade-changelog into .cursor/skills/upgrade-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-changelog", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/akash-network/node.git --path .agents/skills/upgrade-changelog

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add akash-network/node --skill upgrade-changelog -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install akash-network/node upgrade-changelog --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akash-network/node.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/upgrade-changelog .gemini/skills/upgrade-changelog && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "upgrade-changelog" agent skill from https://github.com/akash-network/node/tree/main/.agents/skills/upgrade-changelog into .gemini/skills/upgrade-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-changelog", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install akash-network/node upgrade-changelog

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add akash-network/node --skill upgrade-changelog -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/akash-network/node.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/upgrade-changelog .github/skills/upgrade-changelog && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "upgrade-changelog" agent skill from https://github.com/akash-network/node/tree/main/.agents/skills/upgrade-changelog into .github/skills/upgrade-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-changelog", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add akash-network/node --skill upgrade-changelog -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install akash-network/node upgrade-changelog --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akash-network/node.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/upgrade-changelog .opencode/skills/upgrade-changelog && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "upgrade-changelog" agent skill from https://github.com/akash-network/node/tree/main/.agents/skills/upgrade-changelog into .opencode/skills/upgrade-changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upgrade-changelog", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: upgrade-changelog
GitHub stars: 1.1k
Token cost: ~923 tokens
SKILL.md length: 386 words
Files: 1
Skills in repo: 4
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go

Works in 5 steps: Find semver directories — list all… → Read upgrades/CHANGELOG.md — identify… → For each new version (no existing… → …
Tasks that involve Changelog and release notes
SKILL.md covers Steps and Important notes
Calls go

What it does

Upgrade Changelog is an agent skill from akash-network/node. Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go

Its SKILL.md is about 920 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. The repository describes itself as: Source code for Akash node, a secure, transparent, and peer-to-peer cloud computing network. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Changelog and release notes

Example prompts

“Use the upgrade-changelog skill to generate CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go”
“/upgrade-changelog”

Workflow steps

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

Find semver directories — list all directories under upgrades/software/ whose names match v.. (e.g., v2.0.0, v1.0.0).
Read upgrades/CHANGELOG.md — identify which versions already have entries by scanning for ##### vX.Y.Z headings. If a version already has…
For each new version (no existing heading), gather data from two files
Insert the new entry in upgrades/CHANGELOG.md immediately after the line
Report results — list each version processed and what was added. For skipped versions (already in CHANGELOG), mention they were skipped.

What it can do on your machine

Read from SKILL.md and the folder at commit 5193e54. 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
Shell commands in SKILL.md call:
- go
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

Upgrade Changelog loads about 923 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 386 words of instructions outside code blocks.

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

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 akash-network/node at commit 5193e54, republished under its Apache-2.0 licence (© akash-network). 386 words, ~923 tokens.

Download SKILL.mdSave it as .claude/skills/upgrade-changelog/SKILL.md (or your agent's skills folder).

name: upgrade-changelog
description: Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go

Instructions

Generate changelog entries in upgrades/CHANGELOG.md for any upgrade version under upgrades/software/ that doesn't already have an entry.

Steps

Find semver directories — list all directories under upgrades/software/ whose names match v<major>.<minor>.<patch> (e.g., v2.0.0, v1.0.0).
Read upgrades/CHANGELOG.md — identify which versions already have entries by scanning for ##### vX.Y.Z headings. If a version already has a heading, skip it entirely.
For each new version (no existing heading), gather data from two files:

3a. Parse upgrades/software/<version>/init.go

Find all utypes.RegisterMigration(...) calls. Each call has the form:
go
```
utypes.RegisterMigration(moduleName, version, handlerFn)
```
- moduleName is a Go constant (e.g., dv1.ModuleName). Resolve it:
  1. Find the import alias (e.g., dv1 "pkg.akt.dev/go/node/deployment/v1")
  2. Search the imported package for ModuleName constant definition to get the actual string value
- version is a uint64 — this is the from version. The to version is version + 1.
- Record each migration as: moduleName version -> version+1
3b. Parse upgrades/software/<version>/upgrade.go

Find the StoreLoader() method. It returns a *storetypes.StoreUpgrades struct with optional fields:
- Added: []string{...} — new stores
- Renamed: []storetypes.StoreRename{...} — renamed stores
- Deleted: []string{...} — removed stores
If StoreLoader() returns nil, there are no store changes.

For each store key constant (e.g., epochstypes.StoreKey, ttypes.ModuleName):
1. Find the import alias in the file
2. Search the imported package for the constant definition to get the actual string value
Insert the new entry in upgrades/CHANGELOG.md immediately after the line:
```
Add new upgrades after this line based on the template above
```
followed by -----.

Use this format (newest entries go first, right after the delimiter):
markdown
```
##### vX.Y.Z

###### Description

- Stores
    - added
        - `storeName`: brief description if available
    - renamed
        - `oldName` -> `newName`
    - deleted
        - `storeName`: brief description if available

- Migrations
    - moduleName `from -> to`
```
Omission rules (match existing CHANGELOG style):
- Omit the entire Stores section if there are no added, renamed, or deleted stores
- Omit added/renamed/deleted subsections individually if empty
- Omit the entire Migrations section if there are no migrations
- Always include the ###### Description heading (leave it for the user to fill in)
Report results — list each version processed and what was added. For skipped versions (already in CHANGELOG), mention they were skipped.

Show full SKILL.md (87 more words)Show less

Important notes

Store key constants may be named StoreKey or ModuleName — both are used as store identifiers. Resolve whichever constant appears in the code.
When resolving Go constants from external packages, search under the Go module cache or use go doc if needed. The packages typically follow the pattern pkg.akt.dev/go/node/<module>/<version>.
If a constant cannot be resolved, use the raw Go expression as a placeholder (e.g., `epochstypes.StoreKey`) and warn the user.
Multiple versions may need entries — process them all in one run, inserting newest first after the delimiter.

Files

Just SKILL.md in .agents/skills/upgrade-changelog of akash-network/node.

Open the folder on GitHubat commit 5193e54

Compare with similar skills

Upgrade 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.

Upgrade Changelog compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Upgrade Changelog this skillakash-network/node	1.1k	—	~923	Automated safety check: Pass	Apache-2.0	4 days ago
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
StarRocks Release NotesStarRocks/starrocks	12k	—	~1.9k	Automated safety check: Notes	Apache-2.0	today
Cutting A ReleaseTriliumNext/Trilium	38k	—	~3.2k	Automated safety check: Pass	AGPL-3.0	today
Mole CLI Release Flowtw93/Mole	70k	—	~2.6k	Automated safety check: Pass	GPL-3.0	today
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
12k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check: notes
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
70k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
28k GitHub stars~2.9k tokensUpdated today
DevelopmentAuto-check passed

Questions about Upgrade Changelog

What does Upgrade Changelog do?

Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go. Upgrade Changelog is an agent skill from akash-network/node.

When should I use Upgrade Changelog?

Upgrade Changelog fits situations like: tasks that involve Changelog and release notes.

How do I install Upgrade Changelog in Claude Code?

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

How do I install Upgrade Changelog in Codex?

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

Can I use Upgrade 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 akash-network/node --skill upgrade-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/upgrade-changelog, .gemini/skills/upgrade-changelog, .github/skills/upgrade-changelog and .opencode/skills/upgrade-changelog in your project.

What does Upgrade Changelog need to run?

Going by SKILL.md and its folder, Upgrade Changelog needs the command-line tools its instructions call (go).

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

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

How many tokens does Upgrade Changelog use?

About 923 tokens (SKILL.md is roughly 3.7k 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 Upgrade Changelog?

Skills that share tags, products or a category with Upgrade Changelog: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Mole CLI Release Flow (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Upgrade Changelog?

akash-network (a GitHub organization) maintains it in akash-network/node, which has 1,116 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

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

Upgrade Changelog

Install Upgrade Changelog

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Instructions

Steps

3a. Parse `upgrades/software/<version>/init.go`

3b. Parse `upgrades/software/<version>/upgrade.go`

Important notes

Files

Compare with similar skills

Similar skills

Simple English

StarRocks Release Notes

Cutting A Release

Mole CLI Release Flow

React Router Release Notes Prep

Release

More from akash-network/node

Guidelines

Setup Env

Vanity

Questions about Upgrade Changelog

Install Upgrade Changelog

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Instructions

Steps

3a. Parse upgrades/software/<version>/init.go

3b. Parse upgrades/software/<version>/upgrade.go

Important notes

Files

Compare with similar skills

Similar skills

More from akash-network/node

Related

Questions about Upgrade Changelog

3a. Parse `upgrades/software/<version>/init.go`

3b. Parse `upgrades/software/<version>/upgrade.go`