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.
Tag a new version, create a GitHub release with organized release notes, build all packages, and upload artifacts.
Install Memorains GitHub Release
$ npx skills add redTreeOnWall/memorains --skill memorains-github-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install redTreeOnWall/memorains memorains-github-release --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/redTreeOnWall/memorains.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/memorains-github-release .claude/skills/memorains-github-release && 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 "memorains-github-release" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-github-release into .claude/skills/memorains-github-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-github-release", 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/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-github-releaseType 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 redTreeOnWall/memorains --skill memorains-github-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install redTreeOnWall/memorains memorains-github-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/memorains-github-release .agents/skills/memorains-github-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "memorains-github-release" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-github-release into .agents/skills/memorains-github-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-github-release", 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 redTreeOnWall/memorains --skill memorains-github-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install redTreeOnWall/memorains memorains-github-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/memorains-github-release .cursor/skills/memorains-github-release && 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 "memorains-github-release" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-github-release into .cursor/skills/memorains-github-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-github-release", 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/redTreeOnWall/memorains.git --path .agents/skills/memorains-github-release--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 redTreeOnWall/memorains --skill memorains-github-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install redTreeOnWall/memorains memorains-github-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/memorains-github-release .gemini/skills/memorains-github-release && 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 "memorains-github-release" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-github-release into .gemini/skills/memorains-github-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-github-release", 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 redTreeOnWall/memorains memorains-github-releaseInstalls 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 redTreeOnWall/memorains --skill memorains-github-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/memorains-github-release .github/skills/memorains-github-release && 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 "memorains-github-release" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-github-release into .github/skills/memorains-github-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-github-release", 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 redTreeOnWall/memorains --skill memorains-github-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install redTreeOnWall/memorains memorains-github-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/redTreeOnWall/memorains.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/memorains-github-release .opencode/skills/memorains-github-release && 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 "memorains-github-release" agent skill from https://github.com/redTreeOnWall/memorains/tree/main/.agents/skills/memorains-github-release into .opencode/skills/memorains-github-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "memorains-github-release", 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
memorains-github-release- GitHub stars
- 124
- Token cost
- ~1.3k tokens
- SKILL.md length
- 426 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Tag a new version, create a GitHub release with organized release notes, build all packages, and upload artifacts.
- Works in 8 steps: Determine the version and last release → Review commits since the last release → Write organized release notes → …
- The user wants to release
- SKILL.md covers Prerequisites, Release Steps and Example Release Notes Structure
- Calls gh, git and node
What it does
Memorains GitHub Release is an agent skill from redTreeOnWall/memorains. Tag a new version, create a GitHub release with organized release notes, build all packages, and upload artifacts. Use when the user wants to release, tag, publish, or ship a new version of memorains on GitHub, or mentions putting out a GitHub release.
Its SKILL.md is about 1.3k 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. It works with GitHub. The licence is MIT.
When your agent uses it
- The user wants to release
- Ship a new version of memorains on GitHub
- Mentions putting out a GitHub release
Example prompts
- “/memorains-github-release”
Requirements
- Python 3
- Node.js
- Docker
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a9de01b. 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:
ghgitnodepython3bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and 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
Memorains GitHub Release loads about 1.3k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 426 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 redTreeOnWall/memorains at commit a9de01b, republished under its MIT licence (© redTreeOnWall). 426 words, ~1,300 tokens.
Download SKILL.mdSave it as
.claude/skills/memorains-github-release/SKILL.md (or your agent's skills folder).- name
- memorains-github-release
- description
- Tag a new version, create a GitHub release with organized release notes, build all packages, and upload artifacts. Use when the user wants to release, tag, publish, or ship a new version of memorains on GitHub, or mentions putting out a GitHub release.
Memorains GitHub Release
Create a GitHub release for memorains: tag the version, write release notes by reviewing actual code changes, build all platform packages, and upload them as release assets.
Prerequisites
ghCLI must be installed and authenticated (gh auth status)- Working Node.js and npm setup in
client/andserver/ - Android SDK configured (for
.apkbuilds) script/build_all.shmust be runnable
Release Steps
Execute these in order. Wait for each step to complete before starting the next.
1. Determine the version and last release
Read the current version from client/package.json — this is the version to release:
node -e "console.log(JSON.parse(require('fs').readFileSync('client/package.json')).version)"Then find the latest published GitHub release — this is the baseline for "what changed":
gh release list --limit 5Use the top entry as the last release. If the user mentions a specific prior release (e.g., "since 0.8.68"), prefer that instead.
Release notes should cover all commits since that release tag:
git log <LAST_RELEASE_TAG>..HEAD --oneline --no-decorate2. Review commits since the last release
Get the full list of commits between the last release tag and HEAD:
git log <LAST_RELEASE_TAG>..HEAD --oneline --no-decorateThen, read the actual code diffs — not just commit messages. For each major feature/fix area, inspect the relevant files:
# Get the list of files that changed
git diff --stat <LAST_RELEASE_TAG>..HEAD
# Read diffs for key areas (group by component/feature)
git diff <LAST_RELEASE_TAG>..HEAD -- <file-path>Pay special attention to:
- New files (new features)
client/src/components/— UI componentsclient/src/editor/— editor logicclient/src/utils/— utilitiesclient/src/internationnalization/— new i18n strings
3. Write organized release notes
Group changes by category, not by commit. Use sections like:
- New Features — brand new capabilities
- Improvements — enhancements to existing features
- UI — visual/presentation changes
- Bug Fixes — problems resolved
For each item, write a one-line summary describing what changed from the user's perspective. Include keyboard shortcuts, file paths, or UI positions when relevant. Be specific — prefer "Outline panel with hierarchical tree view, collapsible by heading level" over "added outline".
Write notes to a temp file to avoid shell escaping issues:
# Write to /tmp/release-notes-<VERSION>.md first, then use --notes-file
gh release create <VERSION> --title "v<VERSION>" --notes-file /tmp/release-notes-<VERSION>.mdShow full SKILL.md (143 more words)Show less
4. Create and push the tag
git tag -a <VERSION> -m "<VERSION>: <short summary>"
git push origin <VERSION>5. Create the GitHub release
gh release create <VERSION> \
--title "v<VERSION>" \
--notes-file /tmp/release-notes-<VERSION>.mdVerify the release body afterward:
gh release view <VERSION> --json body | python3 -m json.tool | head -20If the body is truncated (shows only a heading), the notes file content wasn't passed correctly. Re-edit the release:
gh release edit <VERSION> --notes-file /tmp/release-notes-<VERSION>.md6. Build all packages
Run from the script/ directory:
cd <PROJECT_ROOT>/script && bash build_all.shThis produces:
script/out/package.tar.gz— web deploy package (Docker)script/out/memorains-note_<VERSION>_amd64.deb— Linux desktopscript/out/memorains-note-win32-x64-<VERSION>.zip— Windows desktopscript/out/memorains-release.apk— Android (signed)
7. Upload artifacts to the release
cd <PROJECT_ROOT>/script/out && \
gh release upload <VERSION> \
memorains-note_<VERSION>_amd64.deb \
memorains-note-win32-x64-<VERSION>.zip \
memorains-release.apk \
package.tar.gz \
--clobberVerify with:
gh release view <VERSION> --json assets --jq '.assets[] | "\(.name) \(.size | tonumber / 1048576 * 100 | floor / 100)MB"'8. Bump version for next development cycle
After the release, bump the patch version in client/package.json so the next changes start from a fresh version. Do not commit or push — the user will do that when they start the next round of changes.
Example Release Notes Structure
## What's New in v<VERSION>
### ✨ New Features
- Item one
- Item two
### 🔄 Improvements
- Item one
### ⌨️ Keyboard Shortcuts
- **Shortcut** — description
### 🎨 UI Improvements
- Item one
### 🐛 Bug Fixes
- **Bold summary** — detail about the fix
---
_N commits since v<LAST_TAG>_ | _Co-authored-by: pi_Keep notes concise but specific. Every item should tell the reader what changed and why it matters. Avoid vague summaries and group related commits into single bullet points.
© redTreeOnWall, MIT. 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 .agents/skills/memorains-github-release of redTreeOnWall/memorains.
Open the folder on GitHubat commit a9de01b
Compare with similar skills
Memorains GitHub Release 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 |
|---|---|---|---|---|---|---|
| Memorains GitHub Release this skillredTreeOnWall/memorains | 124 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
More from redTreeOnWall/memorains
Memorains DB Backup
redTreeOnWall/memorains
Back up the memorains production database and download the dump to the local backups/ directory.
Memorains Deploy
redTreeOnWall/memorains
Deploy memorains to production servers. An agent skill from redTreeOnWall/memorains.
Related
Works with
Categories
Questions about Memorains GitHub Release
What does Memorains GitHub Release do?
Tag a new version, create a GitHub release with organized release notes, build all packages, and upload artifacts. Memorains GitHub Release is an agent skill from redTreeOnWall/memorains. Tag a new version, create a GitHub release with organized release notes, build all packages, and upload artifacts.
When should I use Memorains GitHub Release?
Memorains GitHub Release fits situations like: the user wants to release; ship a new version of memorains on GitHub; mentions putting out a GitHub release.
How do I install Memorains GitHub Release in Claude Code?
Run `npx skills add redTreeOnWall/memorains --skill memorains-github-release -a claude-code`. Or copy the skill folder (.agents/skills/memorains-github-release in redTreeOnWall/memorains) into .claude/skills/memorains-github-release in your project. Claude Code loads it when a task matches its description.
How do I install Memorains GitHub Release in Codex?
Run `npx skills add redTreeOnWall/memorains --skill memorains-github-release -a codex`. Or copy the skill folder (.agents/skills/memorains-github-release in redTreeOnWall/memorains) into .agents/skills/memorains-github-release in your project. Codex loads it when a task matches its description.
Can I use Memorains GitHub Release 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 redTreeOnWall/memorains --skill memorains-github-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/memorains-github-release, .gemini/skills/memorains-github-release, .github/skills/memorains-github-release and .opencode/skills/memorains-github-release in your project.
What does Memorains GitHub Release need to run?
Going by SKILL.md and its folder, Memorains GitHub Release needs the command-line tools its instructions call (gh, git, node, python3 and bash). Our summary lists: Python 3; Node.js; Docker.
Does Memorains GitHub Release access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Memorains GitHub Release 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 Memorains GitHub Release use?
Memorains GitHub Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Memorains GitHub Release use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Memorains GitHub Release?
Skills that share tags, products or a category with Memorains GitHub Release: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (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 Memorains GitHub Release?
redTreeOnWall (a GitHub user) maintains it in redTreeOnWall/memorains, which has 124 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: redTreeOnWall/memorains on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.