vanity
Registers node major version vanity URL in the sibling vanity repo
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- vanity
- description
- Registers node major version vanity URL in the sibling vanity repo
03 SKILL.md 正文
Instructions
Register the current node major version as a vanity URL in the github.com/com/akash-network/vanity repo.
Steps
-
Read the major version from
go.modin this repo. Extract the version suffix from the module path (e.g.pkg.akt.dev/node/v2→v2). If the module path has no version suffix (v0/v1), abort — no vanity entry is needed. -
Get the current git branch name using
git rev-parse --abbrev-ref HEAD. -
Open
vanity/vangen.jsonand check if a repository entry with"prefix": "node/vN"already exists (wherevNis the version from step 1). If it exists, inform the user and abort. -
Add a new entry to the
repositoriesarray invanity/vangen.json:
{
"prefix": "node/vN",
"type": "git",
"main": true,
"url": "https://github.com/akash-network/node",
"source": {
"home": "https://github.com/akash-network/node",
"dir": "https://github.com/akash-network/node/tree/BRANCH{/dir}",
"file": "https://github.com/akash-network/node/blob/BRANCH{/dir}/{file}#L{line}"
},
"website": {
"url": "https://github.com/akash-network/node"
}
}
Replace vN with the detected version and BRANCH with the detected branch name. Place the entry after the last existing node entry.
-
Run
make vangeninvanityto regenerate HTML files. -
Verify that
vanity/node/vN/index.htmlwas created and contains the correctgo-importandgo-sourcemeta tags pointing to the detected branch. Also verify that existingvanity/node/index.htmland anyvanity/node/vN/index.htmlis unchanged.
04 同仓库更多 Skills
upgrade-changelog
Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go
build-contracts
Builds all cosmwasm contracts
setup-env
Set up development environment by loading direnv. Must be run before any make targets (tests, builds, linting).
guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.