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

Release

by deusXmachina-dev in deusXmachina-dev/memorylane

Prepare a MemoryLane release by updating the version and release notes, then creating and pushing the tagged release commit that triggers CI.

GPL-3.0Auto-check passedDevelopment

Install Release

skills CLI
$ npx skills add deusXmachina-dev/memorylane --skill release -a claude-code

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

GitHub CLI
$ gh skill install deusXmachina-dev/memorylane release --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/deusXmachina-dev/memorylane.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && 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
release
GitHub stars
121
Token cost
~982 tokens
SKILL.md length
415 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
GPL-3.0

At a glance

Prepare a MemoryLane release by updating the version and release notes, then creating and pushing the tagged release commit that triggers CI.

  • Works in 9 steps: Install dependencies → Determine the new version → Review changes since the last tag → …
  • The user asks to release
  • SKILL.md covers Prerequisites, Steps and Checklist
  • Calls git and npm

What it does

Release is an agent skill from deusXmachina-dev/memorylane. Prepare a MemoryLane release by updating the version and release notes, then creating and pushing the tagged release commit that triggers CI. Use when the user asks to release, ship, publish, bump version, or cut a stable or prerelease version.

Its SKILL.md is about 980 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 Git. The licence is GPL-3.0.

When your agent uses it

  • The user asks to release
  • Prerelease version

Example prompts

  • “/release”

Requirements

  • Node.js

Workflow steps

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

  1. Install dependencies
  2. Determine the new version
  3. Review changes since the last tag
  4. Bump version in package.json
  5. Update RELEASE_NOTES.md
  6. Update README.md if needed
  7. Format and lint
  8. Commit and tag
  9. Push the commit and tag

What it can do on your machine

Read from SKILL.md and the folder at commit 16abbe0. 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
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, 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 loads about 982 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 415 words of instructions outside code blocks.

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

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 deusXmachina-dev/memorylane at commit 16abbe0, republished under its GPL-3.0 licence (© deusXmachina-dev). 415 words, ~982 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Prepare a MemoryLane release by updating the version and release notes, then creating and pushing the tagged release commit that triggers CI. Use when the user asks to release, ship, publish, bump version, or cut a stable or prerelease version.

MemoryLane Release Workflow

Use this skill for both normal releases and prereleases. The GitHub Actions release pipeline builds macOS and Windows artifacts after the tagged commit is pushed. Tags without a suffix publish regular releases. Tags with a semver suffix such as -beta.1 publish GitHub prereleases.

Prerequisites

  • Working tree is clean (git status shows nothing to commit)
  • On the main branch, up to date with origin
  • Dependencies installed with npm install

Steps

1. Install dependencies
bash
npm install

Always run this first so all workspace packages are present before any release edits, checks, or git operations.

2. Determine the new version

Ask the user if not provided.

  • Stable: MAJOR.MINOR.PATCH
  • Prerelease: MAJOR.MINOR.PATCH-label.N

The git tag format is always v<version>.

3. Review changes since the last tag
bash
git log --oneline $(git describe --tags --abbrev=0)..HEAD
git diff --stat $(git describe --tags --abbrev=0)..HEAD

Summarize the key user-facing changes. This drives RELEASE_NOTES.md.

4. Bump version in package.json

Update the "version" field to the new version.

5. Update RELEASE_NOTES.md

Follow the existing format in the file. Keep the wording brief and current.

  • Title: # MemoryLane vX.Y.Z
  • What's Changed: Summarize the commits into user-facing bullet points. Reference GitHub issues where applicable (for example closes #4).
  • Features: Update the feature list if new capabilities were added.
  • Known Issues & Limitations: Remove any issues that have been resolved. Add new ones if applicable.
  • Installation: Keep the macOS and Windows install guidance aligned with the current release channel.
  • Full Changelog: Update the tag reference in the URL.
6. Update README.md if needed

Check the "Coming Soon" and "Limitations" sections. If a released feature is listed there, move or remove it.

Show full SKILL.md (164 more words)Show less
7. Format and lint
bash
npm run format
npm run lint
8. Commit and tag

Stage only the files you changed:

bash
git add package.json package-lock.json RELEASE_NOTES.md
# Add README.md only if it changed for this release.
git add README.md
git commit -m "release: vX.Y.Z"
git tag vX.Y.Z

Create the tag only after the commit succeeds. Do not run git commit and git tag in parallel.

If the version is a prerelease, keep the same commit format and tag shape:

bash
git commit -m "release: vX.Y.Z-label.N"
git tag vX.Y.Z-label.N

After tagging, verify it points at the release commit:

bash
git rev-parse HEAD
git rev-parse vX.Y.Z

For prereleases:

bash
git rev-parse HEAD
git rev-parse vX.Y.Z-label.N

These SHAs must match before pushing.

9. Push the commit and tag
bash
git push origin HEAD
git push origin vX.Y.Z

For a prerelease version, push the prerelease tag instead:

bash
git push origin HEAD
git push origin vX.Y.Z-label.N

Pushing the tag triggers .github/workflows/release.yml. That workflow builds both platforms and creates the GitHub release automatically.

Checklist

Before finishing, verify:

  • package.json version matches the new tag
  • package-lock.json version matches the new tag
  • RELEASE_NOTES.md title and changelog link reference the new version
  • Resolved known issues are removed from release notes
  • README.md "Coming Soon" doesn't list shipped features
  • npm install has been run before release steps
  • npm run format and npm run lint pass
  • Commit message matches the version tag
  • The correct v<version> tag is pushed to origin

© deusXmachina-dev, 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 .agents/skills/release of deusXmachina-dev/memorylane.

Open the folder on GitHubat commit 16abbe0

Compare with similar skills

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skilldeusXmachina-dev/memorylane121—~982Automated safety check: PassGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • 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

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

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed

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

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

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

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

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

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from deusXmachina-dev/memorylane

All 9 skills in this repo

  • Makemigrations

    deusXmachina-dev/memorylane

    Create SQLite migrations for MemoryLane storage schema changes.

    121 GitHub stars~973 tokensUpdated yesterday
    Auto-check passed

  • Process Analyst New

    deusXmachina-dev/memorylane

    (new) Find a person's repeated tasks from their screen activity, and what each one is worth automating, with the time and money saved.

    121 GitHub stars~13k tokensUpdated yesterday
    Auto-check: notes

  • Automation Instructions

    deusXmachina-dev/memorylane

    Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).

    121 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Discover Patterns

    deusXmachina-dev/memorylane

    Discover repeated workflow patterns from screen activity and suggest automations

    121 GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed

  • Last 30 Minutes

    deusXmachina-dev/memorylane

    Summarize what you've been doing in the last 30 minutes. An agent skill from deusXmachina-dev/memorylane.

    121 GitHub stars~696 tokensUpdated yesterday
    Auto-check passed

  • Report New

    deusXmachina-dev/memorylane

    (new) Turn a process analysis into a polished, client-ready report, first an HTML deck you review, then a matching PDF.

    121 GitHub stars~7.9k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Release

What does Release do?

Prepare a MemoryLane release by updating the version and release notes, then creating and pushing the tagged release commit that triggers CI. Release is an agent skill from deusXmachina-dev/memorylane. Prepare a MemoryLane release by updating the version and release notes, then creating and pushing the tagged release commit that triggers CI.

When should I use Release?

Release fits situations like: the user asks to release; prerelease version.

How do I install Release in Claude Code?

Run `npx skills add deusXmachina-dev/memorylane --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in deusXmachina-dev/memorylane) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.

How do I install Release in Codex?

Run `npx skills add deusXmachina-dev/memorylane --skill release -a codex`. Or copy the skill folder (.agents/skills/release in deusXmachina-dev/memorylane) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use 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 deusXmachina-dev/memorylane --skill 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/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git and npm). Our summary lists: Node.js.

Does Release access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is 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 Release use?

Release 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 Release use?

About 982 tokens (SKILL.md is roughly 3.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 Release?

Skills that share tags, products or a category with Release: React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

deusXmachina-dev (a GitHub organization) maintains it in deusXmachina-dev/memorylane, which has 121 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.

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