Agent skill

Nylas Nodejs Release

Prepares nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag, and PR body.

MITAuto-check: warningsDevelopment

Install Nylas Nodejs Release

The automated check flagged lines worth reading first. See the safety section below.

skills CLI

$ npx skills add nylas/nylas-nodejs --skill nylas-nodejs-release -a claude-code

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

GitHub CLI

$ gh skill install nylas/nylas-nodejs nylas-nodejs-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/nylas/nylas-nodejs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/nylas-nodejs-release .claude/skills/nylas-nodejs-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/

Paste into Claude Code

Install the "nylas-nodejs-release" agent skill from https://github.com/nylas/nylas-nodejs/tree/main/.cursor/skills/nylas-nodejs-release into .claude/skills/nylas-nodejs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nylas-nodejs-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

$skill-installer install https://github.com/nylas/nylas-nodejs/tree/main/.cursor/skills/nylas-nodejs-release

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

skills CLI

$ npx skills add nylas/nylas-nodejs --skill nylas-nodejs-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nylas/nylas-nodejs nylas-nodejs-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nylas/nylas-nodejs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/nylas-nodejs-release .agents/skills/nylas-nodejs-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "nylas-nodejs-release" agent skill from https://github.com/nylas/nylas-nodejs/tree/main/.cursor/skills/nylas-nodejs-release into .agents/skills/nylas-nodejs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nylas-nodejs-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.

skills CLI

$ npx skills add nylas/nylas-nodejs --skill nylas-nodejs-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nylas/nylas-nodejs nylas-nodejs-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nylas/nylas-nodejs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/nylas-nodejs-release .cursor/skills/nylas-nodejs-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "nylas-nodejs-release" agent skill from https://github.com/nylas/nylas-nodejs/tree/main/.cursor/skills/nylas-nodejs-release into .cursor/skills/nylas-nodejs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nylas-nodejs-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

$ gemini skills install https://github.com/nylas/nylas-nodejs.git --path .cursor/skills/nylas-nodejs-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nylas/nylas-nodejs --skill nylas-nodejs-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nylas/nylas-nodejs nylas-nodejs-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nylas/nylas-nodejs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/nylas-nodejs-release .gemini/skills/nylas-nodejs-release && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "nylas-nodejs-release" agent skill from https://github.com/nylas/nylas-nodejs/tree/main/.cursor/skills/nylas-nodejs-release into .gemini/skills/nylas-nodejs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nylas-nodejs-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.

GitHub CLI

$ gh skill install nylas/nylas-nodejs nylas-nodejs-release

Installs 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).

skills CLI

$ npx skills add nylas/nylas-nodejs --skill nylas-nodejs-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nylas/nylas-nodejs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/nylas-nodejs-release .github/skills/nylas-nodejs-release && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "nylas-nodejs-release" agent skill from https://github.com/nylas/nylas-nodejs/tree/main/.cursor/skills/nylas-nodejs-release into .github/skills/nylas-nodejs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nylas-nodejs-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.

skills CLI

$ npx skills add nylas/nylas-nodejs --skill nylas-nodejs-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nylas/nylas-nodejs nylas-nodejs-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nylas/nylas-nodejs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/nylas-nodejs-release .opencode/skills/nylas-nodejs-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "nylas-nodejs-release" agent skill from https://github.com/nylas/nylas-nodejs/tree/main/.cursor/skills/nylas-nodejs-release into .opencode/skills/nylas-nodejs-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nylas-nodejs-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: nylas-nodejs-release
GitHub stars: 181
Token cost: ~1.6k tokens
SKILL.md length: 640 words
Files: 2
Skills in repo: 1
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Prepares nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag, and PR body.

Works in 3 steps: Branch and changelog (agent) → Version, tag, PR (agent; user may need… → GitHub Release (agent, after confirmation)
The user wants to ship a new SDK version
SKILL.md covers Principles, When the user starts a release, Phase 1 — Branch and changelog… and Phase 2 — Version, tag, PR…, plus 3 more sections
Calls git, npm and gh

What it does

Nylas Nodejs Release is an agent skill from nylas/nylas-nodejs. Prepares nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag, and PR body. Stops for the maintainer to run npm publish, then after confirmation creates the GitHub Release from the tag. Use when the user wants to ship a new SDK version, cut a release branch, update CHANGELOG.md, npm version, tag, open a release PR, publish to npm, or create a GitHub Release.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).

It sits in Development, covering Changelog and release notes and Pull requests. It works with Node.js, npm, GitHub and Git. The repository describes itself as: A NodeJS wrapper for the Nylas REST API for email, contacts, and calendar. The licence is MIT.

When your agent uses it

The user wants to ship a new SDK version
Cut a release branch
Update CHANGELOG.md
Open a release PR

Example prompts

“Use the nylas-nodejs-release skill to prepare nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag…”
“/nylas-nodejs-release”

Requirements

Node.js

Workflow steps

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

Branch and changelog (agent)
Version, tag, PR (agent; user may need to run commands locally)
GitHub Release (agent, after confirmation)

What it can do on your machine

Read from SKILL.md and the folder at commit fabe2d6. 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
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- keepachangelog.com
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

Nylas Nodejs Release loads about 1.6k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 640 words of instructions outside code blocks.

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

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: warnings

The automated check found patterns that need a careful read before installing.

WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:18

**Never** commit or paste npm tokens, `.npmrc` secrets, or session credentials. Publishing uses `npm login` on the main

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 nylas/nylas-nodejs at commit fabe2d6, republished under its MIT licence (© nylas). 640 words, ~1,552 tokens.

Download SKILL.mdSave it as .claude/skills/nylas-nodejs-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: nylas-nodejs-release
description: Prepares nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag, and PR body. Stops for the maintainer to run npm publish, then after confirmation creates the GitHub Release from the tag. Use when the user wants to ship a new SDK version, cut a release branch, update CHANGELOG.md, npm version, tag, open a release PR, publish to npm, or create a GitHub Release.

nylas-nodejs SDK release

Automate everything up to npm publish and GitHub Release creation after merge, with explicit human checkpoints for publishing and confirmation.

Principles

Never commit or paste npm tokens, .npmrc secrets, or session credentials. Publishing uses npm login on the maintainer’s machine only.
Release branch name: vX.Y.Z-release (example: v8.0.5-release).
CHANGELOG follows Keep a Changelog at repo root: CHANGELOG.md.
Traceability: Each changelog line should reference the relevant PR, commit(s), and closed issues where applicable (see PR description template below).

When the user starts a release

Ask for (if not already given):

Target semver X.Y.Z (no leading v in the version number for package.json).
Release date for the changelog (ISO-style: YYYY-MM-DD).
Whether this is latest or canary (see reference.md for canary/dist-tag).

Phase 1 — Branch and changelog (agent)

Ensure work is based on main with intended changes already merged (or document what is included).
Create and checkout vX.Y.Z-release from main:
- git fetch origin main && git checkout -b vX.Y.Z-release origin/main
CHANGELOG.md:
- If there is an ## [Unreleased] section: rename it to ## [X.Y.Z] - YYYY-MM-DD and fill sections (Added / Changed / Fixed / Breaking change, etc.).
- If there is no Unreleased section: add a new top section after the intro paragraphs:
  - ## [X.Y.Z] - YYYY-MM-DD
- Match existing style (see recent entries in CHANGELOG.md).
- For each bullet, include PR/issue links like ([#NNN](https://github.com/nylas/nylas-nodejs/pull/NNN)) where possible.
Commit: chore(release): prepare vX.Y.Z (or team convention).
Push the branch: git push -u origin vX.Y.Z-release.

Stop and show the user: branch name, diff summary, and the new changelog section.

Phase 2 — Version, tag, PR (agent; user may need to run commands locally)

Pre-flight before npm run build / publish: Confirm there are no test files under src/ that would ship in the package (team rule).
Run npm version X.Y.Z (semver only; no v prefix in the command argument).
- This bumps package.json, runs the version lifecycle script (export-version updates src/version.ts for the User-Agent), creates a commit, and a git tag vX.Y.Z (default npm tag prefix).
Push branch and tags:
- git push origin vX.Y.Z-release
- git push origin vX.Y.Z (or git push origin --tags if that is the team norm—prefer pushing the explicit tag to avoid stray tags).

Open a PR vX.Y.Z-release → main with this description template:

markdown

## Release vX.Y.Z (YYYY-MM-DD)

### Changelog

[Paste the full `## [X.Y.Z] - YYYY-MM-DD` section from CHANGELOG.md]

### References

For each line above, link the implementing commits and closed issues (example pattern):

- **Summary of the change** — commit `abc1234` / PR #123 / closes #456 …

(Add community / contributor credits if applicable.)

Ask the user to wait for CI green on the PR.

After CI passes, run npm run build on the release branch to validate the artifact locally.

Show full SKILL.md (245 more words)Show less

Checkpoint — npm publish (maintainer only)
Tell the user clearly:

Publishing requires npm credentials with publish rights, configured via npm login on their machine (see reference.md for prerequisites). Do not store secrets in the repo.
They should run npm publish (or npm publish --tag canary for canary) from the clean release branch after CI passes and build is verified.
They should verify the package on npm when done.

Wait until the user explicitly confirms both:

npm: “The package is published (and dist-tag is correct).”
Git: “The release PR is merged to main.”

Do not create the GitHub Release until both are confirmed.

Phase 3 — GitHub Release (agent, after confirmation)

Only after the user confirms published + PR merged:

Ensure local main is up to date: git fetch origin main && git checkout main && git pull origin main.
Verify tag vX.Y.Z exists on the remote (merged release flow should have the tag from npm version; if not, stop and ask).
Create the GitHub Release from tag vX.Y.Z with:
- Title: vX.Y.Z (or nylas vX.Y.Z to match past releases).
- Body: Same changelog content and PR/issue/commit references as the merged PR; tag community contributors for credit when applicable.

Prefer the gh CLI when available:

bash

gh release create "vX.Y.Z" --title "vX.Y.Z" --notes-file - <<'EOF'
<Paste release notes; same as PR/changelog>
EOF

If gh is not available, give exact GitHub UI steps: Repository → Releases → Draft a new release → choose tag vX.Y.Z → paste notes.

Copy-paste checklist

Track progress in the chat:

text

Phase 1 — Prep
- [ ] Branch vX.Y.Z-release from main
- [ ] CHANGELOG [X.Y.Z] section complete with links
- [ ] Pushed branch

Phase 2 — Version & PR
- [ ] No stray tests under src/
- [ ] npm version X.Y.Z (version.ts + tag)
- [ ] Pushed branch + tag
- [ ] PR opened with changelog + references
- [ ] CI green; npm run build OK
- [ ] User ran npm publish (or canary)
- [ ] User confirmed published + PR merged

Phase 3 — GitHub
- [ ] gh release create (or UI) from vX.Y.Z with full notes

Additional topics

Canary releases, promoting latest, and verifying npm: reference.md
Example release PR style: https://github.com/nylas/nylas-nodejs/pull/590

Files

SKILL.md and 1 other file in .cursor/skills/nylas-nodejs-release of nylas/nylas-nodejs.

SKILL.md
reference.md

Open the folder on GitHubat commit fabe2d6

Compare with similar skills

Nylas Nodejs 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.

Nylas Nodejs Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nylas Nodejs Release this skillnylas/nylas-nodejs	181	—	~1.6k	Automated safety check: Warn	MIT	4 days ago
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	today
ZCF Release AutomationUfoMiao/zcf	6.1k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
Prisma Release PRprisma/orm	48k	—	~4k	Automated safety check: Pass	Apache-2.0	yesterday
Hunk Release Workflowmodem-dev/hunk	9.5k	—	~3.8k	Automated safety check: Pass	MIT	yesterday
AionUi Version BumpiOfficeAI/AionUi	33k	—	~2.1k	Automated safety check: Pass	Apache-2.0	28 days ago

Similar skills

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 today
DevelopmentAuto-check passed
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Prisma Release PR
prisma/orm
Official
Helps a Prisma 8 maintainer cut the next release by bumping the version across every workspace package, opening the release PR and preparing the docs PR.
48k GitHub stars~4k tokensUpdated yesterday
DevelopmentAuto-check passed
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.5k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
AionUi Version Bump
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
33k GitHub stars~2.1k tokensUpdated 28 days ago
DevelopmentAuto-check passed
Deploy Docs
tryonlabs/opentryon
Builds the OpenTryOn Docusaurus site in docs/, commits and pushes to the docs branch, and deploys GitHub Pages (gh-pages).
551 GitHub stars~1.2k tokensUpdated yesterday
DevelopmentAuto-check: notes

Works with

Questions about Nylas Nodejs Release

What does Nylas Nodejs Release do?

Prepares nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag, and PR body. Nylas Nodejs Release is an agent skill from nylas/nylas-nodejs. Prepares nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag, and PR body.

When should I use Nylas Nodejs Release?

Nylas Nodejs Release fits situations like: the user wants to ship a new SDK version; cut a release branch; update CHANGELOG.md; open a release PR.

How do I install Nylas Nodejs Release in Claude Code?

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

How do I install Nylas Nodejs Release in Codex?

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

Can I use Nylas Nodejs 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 nylas/nylas-nodejs --skill nylas-nodejs-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/nylas-nodejs-release, .gemini/skills/nylas-nodejs-release, .github/skills/nylas-nodejs-release and .opencode/skills/nylas-nodejs-release in your project.

What does Nylas Nodejs Release need to run?

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

Does Nylas Nodejs Release access the network?

SKILL.md names 1 domain. As links in the text: keepachangelog.com. This is read from the text; nothing was executed.

Is Nylas Nodejs Release safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Nylas Nodejs Release use?

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

About 1.6k tokens (SKILL.md is roughly 6.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 Nylas Nodejs Release?

Skills that share tags, products or a category with Nylas Nodejs Release: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars), Prisma Release PR (prisma/orm, 48k stars) and Hunk Release Workflow (modem-dev/hunk, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nylas Nodejs Release?

nylas (a GitHub organization) maintains it in nylas/nylas-nodejs, which has 181 GitHub stars. The repository was last updated on October 3, 2026.

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

Install Nylas Nodejs Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

nylas-nodejs SDK release

Principles

When the user starts a release

Phase 1 — Branch and changelog (agent)

Phase 2 — Version, tag, PR (agent; user may need to run commands locally)

Phase 3 — GitHub Release (agent, after confirmation)

Copy-paste checklist

Additional topics

Files

Compare with similar skills

Similar skills

Verdaccio Pull Request Workflow

ZCF Release Automation

Prisma Release PR

Hunk Release Workflow

AionUi Version Bump

Deploy Docs

Related

Questions about Nylas Nodejs Release