Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
This skill creates release notes for new release by reading git commit log.
Install Release Notes
$ npx skills add EvilBeaver/OneScript --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EvilBeaver/OneScript release-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EvilBeaver/OneScript.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/release-notes .claude/skills/release-notes && rm -rf skills-srcUse ~/.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/
Install the "release-notes" agent skill from https://github.com/EvilBeaver/OneScript/tree/develop/.cursor/skills/release-notes into .claude/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 install https://github.com/EvilBeaver/OneScript/tree/develop/.cursor/skills/release-notesType 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.
$ npx skills add EvilBeaver/OneScript --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EvilBeaver/OneScript release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvilBeaver/OneScript.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/release-notes .agents/skills/release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-notes" agent skill from https://github.com/EvilBeaver/OneScript/tree/develop/.cursor/skills/release-notes into .agents/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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.
$ npx skills add EvilBeaver/OneScript --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EvilBeaver/OneScript release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvilBeaver/OneScript.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/release-notes .cursor/skills/release-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-notes" agent skill from https://github.com/EvilBeaver/OneScript/tree/develop/.cursor/skills/release-notes into .cursor/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 https://github.com/EvilBeaver/OneScript.git --path .cursor/skills/release-notes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EvilBeaver/OneScript --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EvilBeaver/OneScript release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvilBeaver/OneScript.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/release-notes .gemini/skills/release-notes && rm -rf skills-srcUse ~/.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/
Install the "release-notes" agent skill from https://github.com/EvilBeaver/OneScript/tree/develop/.cursor/skills/release-notes into .gemini/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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.
$ gh skill install EvilBeaver/OneScript release-notesInstalls 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).
$ npx skills add EvilBeaver/OneScript --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EvilBeaver/OneScript.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/release-notes .github/skills/release-notes && rm -rf skills-srcUse ~/.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/
Install the "release-notes" agent skill from https://github.com/EvilBeaver/OneScript/tree/develop/.cursor/skills/release-notes into .github/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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.
$ npx skills add EvilBeaver/OneScript --skill release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EvilBeaver/OneScript release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EvilBeaver/OneScript.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/release-notes .opencode/skills/release-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-notes" agent skill from https://github.com/EvilBeaver/OneScript/tree/develop/.cursor/skills/release-notes into .opencode/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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
release-notes- GitHub stars
- 587
- Token cost
- ~779 tokens
- SKILL.md length
- 385 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
This skill creates release notes for new release by reading git commit log.
- Works in 4 steps: Определи текущую выпускаемую версию,… → Определи тег предыдущей версии. Для… → Выполни команду gitlog, как показано… → …
- Tasks that involve Changelog and release notes
- SKILL.md covers Формат файла release-notes and Instructions
- Calls git
What it does
Release Notes is an agent skill from EvilBeaver/OneScript. This skill creates release notes for new release by reading git commit log. Use it only when explicitly specified
Its SKILL.md is about 780 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 Commit messages. It works with GitHub. The repository describes itself as: Исполняющая среда скриптов на языке 1С. The licence is MPL-2.0.
When your agent uses it
- Tasks that involve Changelog and release notes
- Tasks that involve Commit messages
Example prompts
- “/release-notes”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Определи текущую выпускаемую версию, прочитав файл Jenkinsfile и его параметр VersionPrefix в самом начале
- Определи тег предыдущей версии. Для этого запроси его у пользователя, если тег не был сразу задан в промпте
- Выполни команду gitlog, как показано выше, для получения истории коммитов между версиями
- Составь дайджест изменений и запиши их в install/release-notes.md
What it can do on your machine
Read from SKILL.md and the folder at commit 8e0d170. 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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Release Notes loads about 779 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 385 words of instructions outside code blocks.
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 EvilBeaver/OneScript at commit 8e0d170, republished under its MPL-2.0 licence (© EvilBeaver). 385 words, ~779 tokens.
Download SKILL.mdSave it as
.claude/skills/release-notes/SKILL.md (or your agent's skills folder).- name
- release-notes
- description
- This skill creates release notes for new release by reading git commit log. Use it only when explicitly specified
Release notes
Когда нужно выпустить новый релиз, в репозитории нужно изменить файл install/release-notes.md (путь относительно корня репозитория)
Для того, чтобы собрать данные, нужно использовать git log и вызвать команду
set LC_ALL=C.UTF-8
set TAGNAME=%1
git --no-pager log --pretty="* %%s" --no-merges %TAGNAME%..HEADгде переменная TAGNAME должна быть git-тэгом предыдущего релиза. Результатом выполнения команды будут тексты коммитов, между TAGNAME и текущим состоянием ветки.
Ты должен запросить у пользователя тег предыдущей версии, либо пользователь тебе сообщит его в промпте сразу.
Далее, ты должен прочитать тексты коммитов, в них могут встречаться ссылки на github issues в виде указания номера задачи через решетку, например вот так:
fixes #1234 bla-bla-bla
Текст коммита также может не содержать упоминания задачи, или быть вовсе техническим/промежуточным коммитом, который в release notes попадать не должен, т.к. не описывает конечное изменение.
Твоя задача и цель - взять тексты коммитов и вывести из них изменения в версии, которые будут включены в файл install/release-notes.md.
Те коммиты, которые содержат ссылки на github - пойти на github в соответствующую задачу в репозитории https://github.com/EvilBeaver/OneScript/issues/<НомерЗадачи> и прочитать ее суть.
Те коммиты, которые ссылок на гитхаб не содержат, ты должен просто прочитать и решить - стоит их включать в release-notes или нет, содержат ли они описание конкретной сделанной функциональности, или это промежуточный, технический и не требующий публикации коммит.
Далее, ты должен сделать итоговый дайджест того, что было сделано в версии и записать это в файл install/release-notes.md. Каждая задача это отдельный bullet-point, причем ссылки на github должны быть сделаны в markdown реальными кликабельными ссылками. Формат строго следующий: сначала ссылка на задачу, потом описание. Если ссылку создать невозможно, тогда только текст задачи.
Show full SKILL.md (139 more words)Show less
Формат файла release-notes
В начале записывается заголовок "Версия <НомерВерсии>. Какая сейчас конкретно версия ты должен посмотреть в файле Jenkinsfile в параметре VersionPrefix и взять его.
Далее идет перечень сделанных задач, как описано выше. Задачи разбиваются на две группы: исправление ошибок и новые возможности. Соответственно в release notes добавляются два раздела уровня "заголовок 2" для "Новые возможности" и "Исправление ошибок". Если задач по какой-то категории нет (например, были только исправления, а новых фич не было), то соответствующий раздел не добавляется в файл совсем.
Instructions
- Определи текущую выпускаемую версию, прочитав файл Jenkinsfile и его параметр VersionPrefix в самом начале
- Определи тег предыдущей версии. Для этого запроси его у пользователя, если тег не был сразу задан в промпте
- Выполни команду gitlog, как показано выше, для получения истории коммитов между версиями
- Составь дайджест изменений и запиши их в install/release-notes.md
© EvilBeaver, MPL-2.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/release-notes of EvilBeaver/OneScript.
Open the folder on GitHubat commit 8e0d170
Compare with similar skills
Release Notes 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Notes this skillEvilBeaver/OneScript | 587 | — | ~779 | Automated safety check: Pass | MPL-2.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Chinese Commit ConventionsjnMetaCode/superpowers-zh | 8.3k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Release Minorknuckleswtf/scribe | 2.3k | — | ~437 | Automated safety check: Pass | MIT | |
| Release WorkflowCaldis/react-zmage | 946 | — | ~3.6k | Automated safety check: Notes | MIT |
Similar skills
Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
Chinese Commit Conventions
jnMetaCode/superpowers-zh
Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.
Release Minor
knuckleswtf/scribe
Automates the process of tagging a new minor release for Scribe by analyzing commit messages, updating the changelog, and creating a GitHub release.
Release Workflow
Caldis/react-zmage
A skill your agent uses when the user wants to ship a new version of react-zmage to npm.
Changeset Changelog
jmfederico/pi-web
A skill your agent uses whenever the user asks about changelogs, Changesets, release notes, conventional commits, commit messages for release notes, or making user-visible project changes that…
Related
Works with
Categories
Questions about Release Notes
What does Release Notes do?
This skill creates release notes for new release by reading git commit log. Release Notes is an agent skill from EvilBeaver/OneScript. This skill creates release notes for new release by reading git commit log.
When should I use Release Notes?
Release Notes fits situations like: tasks that involve Changelog and release notes; tasks that involve Commit messages.
How do I install Release Notes in Claude Code?
Run `npx skills add EvilBeaver/OneScript --skill release-notes -a claude-code`. Or copy the skill folder (.cursor/skills/release-notes in EvilBeaver/OneScript) into .claude/skills/release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Release Notes in Codex?
Run `npx skills add EvilBeaver/OneScript --skill release-notes -a codex`. Or copy the skill folder (.cursor/skills/release-notes in EvilBeaver/OneScript) into .agents/skills/release-notes in your project. Codex loads it when a task matches its description.
Can I use Release Notes 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 EvilBeaver/OneScript --skill release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-notes, .gemini/skills/release-notes, .github/skills/release-notes and .opencode/skills/release-notes in your project.
What does Release Notes need to run?
Going by SKILL.md and its folder, Release Notes needs the command-line tools its instructions call (git).
Does Release Notes access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Notes 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 Release Notes use?
Release Notes is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Notes use?
About 779 tokens (SKILL.md is roughly 3.1k 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 Release Notes?
Skills that share tags, products or a category with Release Notes: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Plane Release Notes Generator (makeplane/plane, 61k stars), Chinese Commit Conventions (jnMetaCode/superpowers-zh, 8.3k stars) and Release Minor (knuckleswtf/scribe, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes?
EvilBeaver (a GitHub user) maintains it in EvilBeaver/OneScript, which has 587 GitHub stars. The repository was last updated on October 5, 2026.
Source: EvilBeaver/OneScript on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.