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 Neva

by nevalang in nevalang/neva

Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts.

MITAuto-check passedDevelopment

Install Release Neva

skills CLI
$ npx skills add nevalang/neva --skill release-neva -a claude-code

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

GitHub CLI
$ gh skill install nevalang/neva release-neva --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/nevalang/neva.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/release-neva .claude/skills/release-neva && 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-neva
GitHub stars
1.1k
Token cost
~1.1k tokens
SKILL.md length
536 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts.

  • Works in 9 steps: Confirm version bump policy before… → Sync to clean, up-to-date main state. → Read release style from recent history. → …
  • Development work in your project
  • SKILL.md covers Overview, Core Tools, Workflow and Guardrails, plus 1 more section
  • Calls gh, git and rg

What it does

Release Neva is an agent skill from nevalang/neva. Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts. Use this for monthly release preparation in nevalang/neva.

Its SKILL.md is about 1.1k 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. It works with GitHub. The repository describes itself as: Dataflow programming language where you write a program as a message-passing graph and everything runs in parallel by default. It has strong static types, compiles to machine… The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/release-neva”

Workflow steps

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

  1. Confirm version bump policy before tagging.
  2. Sync to clean, up-to-date main state.
  3. Read release style from recent history.
  4. Collect merged PRs in the release window.
  5. Bump repository version references.
  6. Draft release notes.
  7. Build assets locally from clean main state.
  8. Create draft release with assets.
  9. Report back.

What it can do on your machine

Read from SKILL.md and the folder at commit 127afd9. 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:

    • gh
    • git
    • rg
    • make

    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

Release Neva loads about 1.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 536 words of instructions outside code blocks.

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

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 nevalang/neva at commit 127afd9, republished under its MIT licence (© nevalang). 536 words, ~1,078 tokens.

Download SKILL.mdSave it as .claude/skills/release-neva/SKILL.md (or your agent's skills folder).
name
release-neva
description
Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts. Use this for monthly release preparation in nevalang/neva.

Neva Release Skill

Overview

Use this skill to prepare a monthly release for nevalang/neva with consistent notes and assets. Default output is a draft GitHub release, not immediate publication.

Core Tools

  • gh (release + PR metadata)
  • git (range and branch state)
  • make (artifact build)
  • shasum (asset checksums)
  • GitHub web UI (optional final review/publish)

Workflow

  1. Confirm version bump policy before tagging.
    • If the bump is ambiguous, ask explicitly: patch or minor.
    • Default to patch for internal-only changes (CI, docs, lint, infra, refactors without user-facing behavior change).
    • Use minor for user-facing language/stdlib/CLI features or meaningful behavior additions.
    • major is out of routine flow; always ask.
  2. Sync to clean, up-to-date main state.
    • git fetch origin --tags --prune
    • ensure working tree is clean
    • ensure build source equals origin/main (or use a clean worktree from it)
  3. Read release style from recent history.
    • inspect 1-2 previous release notes via gh release view ... --json body,publishedAt
    • do not download previous binary assets
  4. Collect merged PRs in the release window.
    • determine range from previous tag (for example vX.Y.Z..origin/main)
    • gather merged PR numbers and read each PR description (gh pr view)
  5. Bump repository version references.
    • update pkg/version.go to the next release version without the v prefix
    • update checked-in Neva manifests and examples that pin the current language version (std/neva.yml, examples/neva.yml, benchmarks/neva.yml, e2e/**/neva.yml, and internal test manifests)
    • update docs and tests that show or assert the current version
    • update generated headers only when they embed the current version string
    • run rg "v?X\\.Y\\.Z" for the previous version and inspect every remaining hit; only leave historical changelog/release-note references intentionally
  6. Draft release notes.
    • keep style concise and factual
    • include: theme/title, summary, key sections, related PR list, full changelog compare link
    • if changes are mostly internal, say that directly
    • include examples for user-facing changes:
      • CLI changes: add at least one command snippet showing new command/flag usage
      • language changes: add at least one Nevalang code snippet
    • keep examples small; full compilable wrappers are optional
  7. Build assets locally from clean main state.
    • make build
    • verify expected platform binaries are present
    • compute checksums with shasum -a 256
  8. Create draft release with assets.
    • gh release create <tag> <assets...> --target main --title <tag> --notes-file <file> --draft
    • verify metadata and uploaded assets via gh release view <tag> --json ...
  9. Report back.
    • release URL
    • included PRs
    • asset names and checksums
    • note whether release remains draft (default)
Show full SKILL.md (145 more words)Show less

Guardrails

  • Do not publish the release unless explicitly requested.
  • Do not invent release claims not supported by merged PR descriptions.
  • Prefer gh over ad-hoc API calls where possible.
  • Keep the skill lightweight; avoid scripts unless explicitly requested.
  • Do not pad examples with unnecessary boilerplate (def Main, imports, full component wrappers) when a focused snippet is enough.

Example Quality Check (Nevalang)

When release notes include Nevalang snippets, they must be concise but real.

  1. Keep snippets minimal.
    • Prefer showing only the relevant node declarations + --- + connections when that explains the change.
    • Full compile-ready files are optional.
  2. Keep snippets language-true.
    • syntax must match current grammar (internal/compiler/parser/neva.g4)
    • semantics should follow project invariants from AGENTS.md (for example Main port shape, chaining rules, [*] bypass form)
  3. Sanity-check against real code.
    • compare syntax patterns with 1-2 existing examples (examples/**/*.neva)
    • if confidence is low, rewrite to a simpler canonical form before publishing

© nevalang, 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 .codex/skills/release-neva of nevalang/neva.

Open the folder on GitHubat commit 127afd9

Compare with similar skills

Release Neva 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 Neva compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Neva this skillnevalang/neva1.1k—~1.1kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

More from nevalang/neva

All 8 skills in this repo

  • Neva To Mermaid

    nevalang/neva

    Convert Neva programs to valid Mermaid flowchart diagrams. An agent skill from nevalang/neva.

    1.1k GitHub stars~795 tokensUpdated 1 mo ago
    Auto-check passed

  • Release Discord Post

    nevalang/neva

    Create a Discord-ready Neva release announcement from a GitHub release payload.

    1.1k GitHub stars~500 tokensUpdated 1 mo ago
    Auto-check passed

  • Release Telegram Post

    nevalang/neva

    Create a Telegram-ready Neva release announcement from a GitHub release payload.

    1.1k GitHub stars~439 tokensUpdated 1 mo ago
    Auto-check passed

  • Papercut

    nevalang/neva

    Capture or triage small Neva repository and engineering-harness frictions without derailing feature work.

    1.1k GitHub stars~400 tokensUpdated 1 mo ago
    Auto-check passed

  • Review

    nevalang/neva

    A skill your agent uses for focused review of a Neva pull request, branch, diff, or patch.

    1.1k GitHub stars~382 tokensUpdated 1 mo ago
    Auto-check passed

  • Go

    nevalang/neva

    A skill your agent uses for Go changes in Neva: authoring, refactoring, debugging, or review.

    1.1k GitHub stars~388 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Release Neva

What does Release Neva do?

Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts. Release Neva is an agent skill from nevalang/neva. Prepare a Neva GitHub release draft from merged PRs, previous release style, and local multi-platform artifacts.

When should I use Release Neva?

Release Neva fits situations like: development work in your project.

How do I install Release Neva in Claude Code?

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

How do I install Release Neva in Codex?

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

Can I use Release Neva 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 nevalang/neva --skill release-neva -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-neva, .gemini/skills/release-neva, .github/skills/release-neva and .opencode/skills/release-neva in your project.

What does Release Neva need to run?

Going by SKILL.md and its folder, Release Neva needs the command-line tools its instructions call (gh, git, rg and make).

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

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

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Neva?

Skills that share tags, products or a category with Release Neva: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Neva?

nevalang (a GitHub organization) maintains it in nevalang/neva, which has 1,085 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 23, 2026.

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