agentmods.dev

release

release is a skill for Claude Code from feniix/pi-extensions. It costs 38 tokens per session (1,136 once invoked), scanned A, original, MIT.

A release workflow for publishing a new version of a software project. It reviews commits, updates the version, creates release notes, and publishes the release on GitHub.

In plain words
What is it for?
Use it when bumping a version, cutting a release, publishing a release, or preparing a changelog from recent commits.
Why use it?
It removes the repeated manual steps involved in deciding the version number, recording changes, committing them, and publishing the result. It also checks that the branch, working tree, and continuous integration checks are ready.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter.

not rated 25repo changed 26d ago A scan SkillSpector: pass 38 tokens original MIT

Good fit Use it when bumping a version, cutting a release, publishing a release, or preparing a changelog from recent commits.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/feniix/pi-extensions/release
View source ↗ feniix/pi-extensions feniix-hq.net
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add feniix/pi-extensions --skill release
Clone the repo
git clone --depth 1 https://github.com/feniix/pi-extensions

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/feniix/pi-extensions/release/github.svg)](https://agentmods.dev/skills/feniix/pi-extensions/release)
Your own site
<a href="https://agentmods.dev/skills/feniix/pi-extensions/release"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/feniix/pi-extensions/release"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,136 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01136
Opus 5.5 $0.00015 $0.00454
Sonnet 5.5 $0.00008 $0.00227
Haiku 4.5 $0.00004 $0.00114

Measured 26d ago against content hash 613476b9f96f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 26d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/pi-devtools/skills/release/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Workflow

Automates release: analyze commits, bump version, generate changelog, commit, push, and create GitHub release.

Tool Restrictions (Critical)

Use these tools:

  • read - Inspect the target package manifest and changelog
  • apply_patch - Maintain the target package's CHANGELOG.md
  • bash - Run repository changelog validation and workspace lockfile reconciliation when applicable
  • devtools_get_repo_info - Verify the active worktree branch and status
  • devtools_check_ci - Check CI status on the default branch
  • devtools_get_latest_tag - Get current version
  • devtools_analyze_commits - Analyze commits for version bump
  • devtools_bump_version - Update package.json
  • devtools_commit - Commit version bump
  • devtools_push - Push changes
  • devtools_create_release - Create GitHub release

Preconditions

Verify these before starting in Pi's active working directory:

  1. The active worktree is on the repository's default branch (devtools_get_repo_info)
  2. The active working tree is clean (no uncommitted changes)
  3. CI is passing on the default branch (devtools_check_ci)

The default branch may already be checked out in another worktree. If the active worktree is not on it, stop and explain which worktree context is active; do not switch branches or modify the other worktree. If any precondition fails, stop and explain.

Process

Step 1: Analyze Commits

Call devtools_analyze_commits to:

  • Find commits since last tag
  • Determine bump type (major/minor/patch)
  • Get suggested new version

Present to user:

  • Show commits grouped by type
  • Show suggested version bump
  • Ask for confirmation or override

Step 2: Bump Version

After user confirms:

  1. Identify the target package's manifest; in a workspace, select exactly one child package rather than the private root. Ask the user if the target is ambiguous.
  2. Call devtools_bump_version with new version and the target manifest's relative file path. In this pnpm workspace, reconcile with pnpm install --lockfile-only and verify pnpm install --frozen-lockfile.
  3. Show the change to user

Read the full file on GitHub · 133 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 26d ago Changed · +11 lines 613476b9f96f
  2. 1mo ago First seen · 122 lines · 38 tokens per session scan A 8f1a2cfc67f4

Subscribe to this mod's changes

release is a skill published in the GitHub repository feniix/pi-extensions (25 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 1,136 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflowReleasesTypeScriptai-agentscoding-agentsdeveloper-toolsmcppi
Related

Other skills, from other repositories

pi-package-sandbox-test

Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.

spences10/my-pi · 40 tokens

pi-release-workflow

Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.

spences10/my-pi · 38 tokens

pi-review-gated-delivery

Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.

spences10/my-pi · 40 tokens

changelog

Create engaging changelogs for recent merges to main branch.

gvkhosla/compound-engineering-pi · 14 tokens

draft-release-notes

Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…

prisma/orm · 174 tokens

publish-npm-version

Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…

prisma/orm · 182 tokens