Agent skill

Prepare Release

by ayutaz in ayutaz/piper-plus

9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き…

MITAuto-check passedDevelopment

Install Prepare Release

skills CLI
$ npx skills add ayutaz/piper-plus --skill prepare-release -a claude-code

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

GitHub CLI
$ gh skill install ayutaz/piper-plus prepare-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/ayutaz/piper-plus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prepare-release .claude/skills/prepare-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
prepare-release
GitHub stars
220
Token cost
~2k tokens
SKILL.md length
575 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き…

  • Works in 6 steps: First: wasm-g2p-v (npm @piper-plus/g2p)… → Second: npm-v (npm piper-plus、 g2p に依存) → Third: dev-create-release.yml を… → …
  • Tasks that involve iOS development
  • SKILL.md covers カバー範囲, 引数, 現在の状態 and フェーズ 1: 現 manifest version…, plus 10 more sections
  • Calls uv, npm and gh; reaches pypi.org and crates.io

What it does

Prepare Release is an agent skill from ayutaz/piper-plus. 9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き publish ガイドを生成する。

Its SKILL.md is about 2k 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 iOS development, Changelog and release notes and Markdown. It works with npm, Rust, C# and Python. The repository describes itself as: Multilingual neural TTS (6 languages: JA/EN/ZH/ES/FR/PT, code supports SV) — C++, C, Rust, Go, Python, npm (WASM). VITS + Prosody, streaming, CUDA/CoreML/DirectML. pip install…. The licence is MIT.

When your agent uses it

  • Tasks that involve iOS development
  • Tasks that involve Changelog and release notes
  • Tasks that involve Markdown

Example prompts

  • “/prepare-release”

Requirements

  • Python 3
  • Node.js
  • Docker
  • Pre-approved tools (allowed-tools): Bash(cat *), Bash(grep *), Bash(jq *), Bash(rg *), Bash(awk *), Bash(curl -s *), Bash(npm view *), Bash(git diff *), Bash(git log *), Bash(git status *), Bash(swift package compute-checksum *), Read, Edit, Grep

Workflow steps

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

  1. First: wasm-g2p-v (npm @piper-plus/g2p) — g2p に変更が無く既公開なら skip
  2. Second: npm-v (npm piper-plus、 g2p に依存)
  3. Third: dev-create-release.yml を workflow_dispatch (version 入力) で実行
  4. Fourth: kotlin-g2p-v (Maven Central、 独立) — 既公開なら skip
  5. Fifth: Package.swift の checksum を pre-tag 更新 (フェーズ 5 の workflow_dispatch artifact から compute-checksum → dev に commit)
  6. Last: その checksum commit に v tag を push → release-shared-lib.yml (libpiper_plus + iOS/Android xcframework)

What it can do on your machine

Read from SKILL.md and the folder at commit 9c6946e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(cat *)
    • Bash(grep *)
    • Bash(jq *)
    • Bash(rg *)
    • Bash(awk *)
    • Bash(curl -s *)
    • Bash(npm view *)
    • Bash(git diff *)
    • Bash(git log *)
    • Bash(git status *)

    …and 4 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv
    • npm
    • gh
    • curl
    • jq
    • swift
    • git
    • cargo

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • pypi.org
    • crates.io
    • api.nuget.org
    • search.maven.org

    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

Prepare Release loads about 2k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 575 words of instructions outside code blocks.

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

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 ayutaz/piper-plus at commit 9c6946e, republished under its MIT licence (© ayutaz). 575 words, ~1,966 tokens.

Download SKILL.mdSave it as .claude/skills/prepare-release/SKILL.md (or your agent's skills folder).
name
prepare-release
description
9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。`release-prep` (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き publish ガイドを生成する。
allowed-tools
Bash(cat *), Bash(grep *), Bash(jq *), Bash(rg *), Bash(awk *), Bash(curl -s *), Bash(npm view *), Bash(git diff *), Bash(git log *), Bash(git status *), Bash(swift package compute-checksum *), Read, Edit, Grep
argument-hint
<runtime|all> --target-version X.Y.Z [--dry-run]
disable-model-invocation
true

Release Preparation Skill (Bump 適用版)

release-prep (read-mostly な確認) の続きとして、 実際の version bump 差分 を全 manifest にわたり生成する skill。

ユーザは memory feedback_conservative_changes.md / feedback_merge_caution.md に従い、 適用は明示確認を取ってから (デフォルト dry-run、 markdown diff 提示のみ)。

カバー範囲

段階対応
Version 散在検出9 manifest を一括 bump 案として markdown 出力
Lockfile 再生成uv.lock / Cargo.lock / package-lock.json の更新コマンド提示
Swift checksumxcframework artifact 取得後の swift package compute-checksum 手順
CHANGELOG 昇格[Unreleased] → [X.Y.Z] - YYYY-MM-DD の markdown diff
Tag 順序ガイドnpm tag (g2p 先行) / shared-lib tag / 内部 chain tag の順序
公開後検証各 registry で publish 完了確認の手順

引数

  • $ARGUMENTS 1 つ目: all / python / rust / csharp / npm / swift / kotlin
  • --target-version X.Y.Z: 次回リリース version (必須)
  • --dry-run (default): markdown 出力のみ、 ファイル変更しない
  • --apply: dry-run の確認後にユーザが追加で渡す flag。 これがある時のみ Edit を実行

現在の状態

  • ブランチ: !git rev-parse --abbrev-ref HEAD
  • 引数: $ARGUMENTS
  • 直近 tag: !git tag --sort=-v:refname | head -3

フェーズ 1: 現 manifest version 読み出し (9 ファイル)

並列で Read し、 各 manifest の現 version を抽出:

RuntimeManifest抽出キー
PythonVERSIONファイル全体
Python (g2p)src/python/g2p/pyproject.toml[project].version
Rustsrc/rust/Cargo.toml[workspace.package].version
C# Coresrc/csharp/PiperPlus.Core/PiperPlus.Core.csproj<Version>
C# Clisrc/csharp/PiperPlus.Cli/PiperPlus.Cli.csproj<Version>
npm synthsrc/wasm/openjtalk-web/package.json.version
npm g2psrc/wasm/g2p/package.json.version
SwiftPackage.swiftlet version = 行 + let g2pVersion = 行
Kotlinandroid/gradle.propertiesVERSION_NAME=

フェーズ 2: 既存 sync gate との交差確認

bash
uv run python scripts/check_voice_catalog_parity.py 2>&1 | tail -3
uv run python scripts/check_ort_versions.py 2>&1 | tail -3
uv run python scripts/check_openjtalk_version_sync.py 2>&1 | tail -3
uv run python scripts/check_ruff_version_sync.py 2>&1 | tail -3
uv run python scripts/check_migration_changelog_parity.py 2>&1 | tail -3

drift があれば bump 前に修復するよう警告。

フェーズ 3: Bump diff の markdown 提示

--target-version を基準に、 該当 runtime の manifest 全てに対する diff を markdown 出力:

出力例 (markdown):

  • Python (VERSION): 1.12.0 → 2.0.0
  • Rust (src/rust/Cargo.toml [workspace.package].version): 0.4.0 → 0.5.0
  • npm synth (src/wasm/openjtalk-web/package.json): 0.6.0 → 0.7.0

all の場合は 9 manifest 全てを順次出力する。

フェーズ 4: Lockfile 再生成手順

bash
# Python
uv lock --upgrade-package piper-plus
# Rust
(cd src/rust && cargo update -p piper-plus)
# npm synth
(cd src/wasm/openjtalk-web && npm install --package-lock-only)
# npm g2p
(cd src/wasm/g2p && npm install --package-lock-only)

--apply 時は順次実行、 そうでなければコマンドのみ表示。

フェーズ 5: Swift checksum 計算ガイド

Package.swift の checksum / g2pChecksum は tag commit に存在していなければならない (SwiftPM は tag の git ref の manifest を解決し、checksum 不一致なら artifact has changed checksum で fail。release-shared-lib.yml の release job も tag push 時に placeholder / 不一致を hard-fail させる)。よって tag push 前 に実施する (gh release download は release がまだ無いので使えない):

bash
# 1. release-shared-lib.yml を tag 無しで workflow_dispatch 実行し artifact を生成
gh workflow run release-shared-lib.yml --ref dev
# 完了後、run の workflow artifact を取得 (release ではない)
gh run download <run-id> --name libpiper_plus-ios-xcframework
# g2pChecksum は g2pVersion が今回 tag と一致する時のみ取得・更新
gh run download <run-id> --name libpiper_plus_g2p-apple-xcframework

# 2. swift package compute-checksum (workflow artifact のファイル名は version 無し)
swift package compute-checksum libpiper_plus-ios.xcframework.zip
swift package compute-checksum libpiper_plus_g2p-apple.xcframework.zip   # g2pVersion == TARGET のみ

# 3. Package.swift の `let checksum` (synthesis) を更新。
#    `let g2pChecksum` は g2pVersion が今回 tag と一致する時のみ更新
#    (異なる場合 release-shared-lib.yml が g2p checksum 検証を自動 skip する)。

# 4. dev に commit し、その commit に v<TARGET_VERSION> tag を push (フェーズ 7 の順序)

workflow_dispatch build と tag build は deterministic なので checksum は一致する。この手順は tag push の直前 (フェーズ 7)。 dry-run でも手順を出力する。

フェーズ 6: CHANGELOG 昇格 markdown diff

bash
awk '/^## \[Unreleased\]/{flag=1; next} /^## /{flag=0} flag' CHANGELOG.md

を抽出し、 以下を提案:

markdown
## [<TARGET_VERSION>] - <YYYY-MM-DD>

(Unreleased から移動した内容)

## [Unreleased]

(空 or next-version 着手項目)

--apply で直接 Edit、 そうでなければ diff のみ出力。

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

フェーズ 7: Publish 順序ガイド

CONTRIBUTING.md の規約に従い、 tag push 順序を明示:

  1. First: wasm-g2p-v<X.Y.Z> (npm @piper-plus/g2p) — g2p に変更が無く既公開なら skip
  2. Second: npm-v<X.Y.Z> (npm piper-plus、 g2p に依存)
  3. Third: dev-create-release.yml を workflow_dispatch (version 入力) で実行 → PyPI / crates.io / NuGet を sleep 30 入りで連鎖 publish。 tag 駆動ではない (Actions UI から手動実行)
  4. Fourth: kotlin-g2p-v<X.Y.Z> (Maven Central、 独立) — 既公開なら skip
  5. Fifth: Package.swift の checksum を pre-tag 更新 (フェーズ 5 の workflow_dispatch artifact から compute-checksum → dev に commit)
  6. Last: その checksum commit に v<X.Y.Z> tag を push → release-shared-lib.yml (libpiper_plus + iOS/Android xcframework)

重要 (フェーズ 5 参照): Swift checksum 更新は v<X.Y.Z> tag の 前 (ステップ 5)。 placeholder のまま tag を push すると release-shared-lib.yml の release job が hard-fail し、 post-tag の後追い PR では SwiftPM 解決を救済できない (tag の git ref が解決対象のため)。

順序逆転による npm install 失敗 (g2p が無いと piper-plus install fail) も防ぐ。 v<X.Y.Z> tag は release-shared-lib.yml と docker-build.yml を同時発火させ、 Docker image (<X.Y.Z> / latest) も自動 publish される点に留意。

フェーズ 8: 公開後検証コマンド

bash
# 各 registry で publish 完了を確認
curl -s https://pypi.org/pypi/piper-plus/json | jq -r '.info.version'
curl -s https://crates.io/api/v1/crates/piper-plus | jq -r '.crate.max_version'
npm view piper-plus version
npm view @piper-plus/g2p version
curl -s "https://api.nuget.org/v3-flatcontainer/piperplus.core/index.json" | jq -r '.versions[-1]'
curl -s "https://search.maven.org/solrsearch/select?q=g:io.github.ayutaz+AND+a:piper-plus-g2p-android&rows=1&wt=json" | jq -r '.response.docs[0].latestVersion'

target version と一致するまで sleep 30 で polling、 30 分以内に揃わなければエラー報告。

注意

  • 既存 release-prep skill との関係: release-prep は「現状の version 散在確認」、 本 skill は「次回 version へ bump する適用案生成」。 先に release-prep で drift を解消してから本 skill を使う流れが推奨。
  • memory feedback_merge_caution.md: tag push / publish に類する操作は本 skill では実行しない。 手順表示のみ。
  • memory feedback_pr_no_milestones.md: マイルストーン番号付与しない。
  • memory feedback_data_asset_distribution.md: data asset 追加時の 7 manifest 同時更新も本 skill では確認のみ。
  • --dry-run がデフォルト で、 --apply は明示指定が必要。

使用例

text
# 全 runtime の v2.0.0 リリース bump 案を生成 (dry-run)
/prepare-release all --target-version 2.0.0

# Python だけ確定、 適用
/prepare-release python --target-version 2.0.0 --apply

# Rust 0.5.0 リリース、 lockfile 再生成手順のみ表示
/prepare-release rust --target-version 0.5.0

期待効果

  • リリース時の 9 manifest 同時 bump を 1 skill に集約 (現状: 手動 Read + Edit + Lock 再生成 + tag 順序記憶)
  • npm tag 順序違反 (g2p 先行必須) を強制チェック
  • Swift checksum 漏れ の防止 (release-shared-lib.yml で fail する前にガイド)
  • CHANGELOG [Unreleased] 昇格 の規定化 (現状: 手動 markdown 編集)
  • publish 後検証 の自動化 (target version が registry に届くまで polling)

© ayutaz, 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 .claude/skills/prepare-release of ayutaz/piper-plus.

Open the folder on GitHubat commit 9c6946e

Compare with similar skills

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

Prepare Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prepare Release this skillayutaz/piper-plus220—~2kAutomated safety check: PassMIT
Build Teaql Appteaql/teaql-agent-kit2.8k—~4.6kAutomated safety check: PassMIT
Fory Performance Optimizationapache/fory4.6k—~2.2kAutomated safety check: PassApache-2.0
MCP SDK Tier Auditmodelcontextprotocol/conformance129—~4.4kAutomated safety check: PassCustom licence
Dbgtheodo-group/debug-that158—~2.2kAutomated safety check: PassMIT
Code Revieweralirezarezvani/claude-skills28k1 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Build Teaql App

    teaql/teaql-agent-kit

    Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries.

    2.8k GitHub stars~4.6k tokensUpdated 11 days ago
    MobileAuto-check passed
  • Run profile-driven bottleneck optimization across Apache Fory implementations (Java, C++, Python/Cython, Go, Rust, Swift, C, JavaScript/TypeScript, Dart, Kotlin, Scala).

    4.6k GitHub stars~2.2k tokensUpdated yesterday
    MobileAuto-check passed
  • MCP SDK Tier Audit

    modelcontextprotocol/conformance

    Official

    Comprehensive tier assessment for an MCP SDK repository against SEP-1730.

    129 GitHub stars~4.4k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Dbg

    theodo-group/debug-that

    Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.

    158 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Code Reviewer

    alirezarezvani/claude-skills

    Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter.

    28k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Release Skills

    nexmoe/eve

    Universal release workflow. An agent skill from nexmoe/eve.

    421 GitHub starsUsed in 3 repos~3.3k tokens
    DevelopmentAuto-check passed

More from ayutaz/piper-plus

All 20 skills in this repo
  • Skill Health

    ayutaz/piper-plus

    .claude/skills//SKILL.md の frontmatter / referenced script 実在 / trigger 衝突 / .claude/hooks/.sh の executable+shebang を検査する meta-skill。

    220 GitHub stars~626 tokensUpdated today
    Auto-check passed
  • Bump Deps

    ayutaz/piper-plus

    ORT / openjtalk / ruff のような cross-runtime に canonical sync が必要な依存関係を 1 コマンドで bump する read-mostly skill。

    220 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Check Cross Runtime

    ayutaz/piper-plus

    Python canonical (src/pythonrun/piperplus/, src/python/pipertrain/, src/python/g2p/piperplusg2p/) を変更した PR で、 ONNX I/O 以外の追随漏れ (phonemizer / config schema / CLI flag / data 形式 / API 変更) を 7 ランタイム +…

    220 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Check Loanword

    ayutaz/piper-plus

    ZH-EN code-switching loanword の同期と forward-compat を 1 コマンドで検査。zhenloanword.json を編集したり 5 ランタイムのいずれかに新規エントリを追加する前後に呼ぶ。Python source を canonical とし、Rust×2 / Go / C / WASM / C++ の 6 mirror + Python…

    220 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Check New Runtime Asset

    ayutaz/piper-plus

    新規データアセット (JSON/TOML) を追加した PR で「7 箇所の package metadata 更新が全て揃っているか」を 1 コマンドで確認。MANIFEST.in / pyproject package-data / Cargo features / npm files / C Content / Android assets / SPM resources の更新漏れを…

    220 GitHub stars~964 tokensUpdated today
    Auto-check passed
  • Check PR Ready

    ayutaz/piper-plus

    PR 作成前の最終チェックリスト (lint/test/docs/CHANGELOG/未コミット確認)。/precheck の拡張版で、ドキュメント整合性も検証します。

    220 GitHub stars~687 tokensUpdated today
    Auto-check passed

Questions about Prepare Release

What does Prepare Release do?

9 パッケージ × 5 レジストリの version bump と関連ファイル更新 (Cargo.lock / package-lock.json / Swift checksum / CHANGELOG 昇格) を 1 コマンドで適用案にする read-mostly skill。release-prep (確認用) の続きに呼び、 実 bump 差分の markdown 提案 + 順序付き…. Prepare Release is an agent skill from ayutaz/piper-plus.

When should I use Prepare Release?

Prepare Release fits situations like: tasks that involve iOS development; tasks that involve Changelog and release notes; tasks that involve Markdown.

How do I install Prepare Release in Claude Code?

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

How do I install Prepare Release in Codex?

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

Can I use Prepare 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 ayutaz/piper-plus --skill prepare-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/prepare-release, .gemini/skills/prepare-release, .github/skills/prepare-release and .opencode/skills/prepare-release in your project.

What does Prepare Release need to run?

Going by SKILL.md and its folder, Prepare Release needs the command-line tools its instructions call (uv, npm, gh, curl, jq and swift). Our summary lists: Python 3; Node.js; Docker. Its frontmatter pre-approves these tools: Bash(cat *), Bash(grep *), Bash(jq *), Bash(rg *), Bash(awk *), Bash(curl -s *), Bash(npm view *), Bash(git diff *), Bash(git log *), Bash(git status *), Bash(swift package compute-checksum *), Read, Edit, Grep.

Does Prepare Release access the network?

SKILL.md names 4 domains. In commands or code: pypi.org, crates.io, api.nuget.org and search.maven.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

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

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

About 2k tokens (SKILL.md is roughly 7.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 Prepare Release?

Skills that share tags, products or a category with Prepare Release: Build Teaql App (teaql/teaql-agent-kit, 2.8k stars), Fory Performance Optimization (apache/fory, 4.6k stars), MCP SDK Tier Audit (modelcontextprotocol/conformance, 129 stars) and Dbg (theodo-group/debug-that, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prepare Release?

ayutaz (a GitHub user) maintains it in ayutaz/piper-plus, which has 220 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.

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