release — for Claude Code release, community, for Claude Code, ide skills, agent-infrastructure, ai-agents, developer-tools, effect-ts, local-first, sqlite

v1.0.0
GitHub

このスキルについて

適した場面: Ideal for AI agents that need use this skill when shipping a new tx version. ローカライズされた概要: # Release Use this skill when shipping a new tx version. It covers agent-infrastructure, ai-agents, cli workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

機能

Use this skill when shipping a new tx version.
Run the local preflight:
node scripts/release-preflight.mjs <version
Run the release gates:
bun run sync-readme

# Core Topics

for Claude Code agent-infrastructure ai-agents developer-tools effect-ts local-first
jamesaphoenix jamesaphoenix
[3]
[1]
Updated: 4/28/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
49
Canonical Locale
en
Detected Body Locale
en

適した場面: Ideal for AI agents that need use this skill when shipping a new tx version. ローカライズされた概要: # Release Use this skill when shipping a new tx version. It covers agent-infrastructure, ai-agents, cli workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

このスキルを使用する理由

推奨ポイント: release helps agents use this skill when shipping a new tx version. Release Use this skill when shipping a new tx version. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

おすすめ

適した場面: Ideal for AI agents that need use this skill when shipping a new tx version.

↓ 実現可能なユースケース for release

ユースケース: Applying Use this skill when shipping a new tx version
ユースケース: Applying Run the local preflight:
ユースケース: Applying node scripts/release-preflight.mjs <version

! セキュリティと制限

  • 制約事項: Do not stop at tag creation. The release is not done until publish.yml succeeds.
  • 制約事項: Do not stop at tag creation
  • 制約事項: Requires repository-specific context from the skill documentation

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is release?

適した場面: Ideal for AI agents that need use this skill when shipping a new tx version. ローカライズされた概要: # Release Use this skill when shipping a new tx version. It covers agent-infrastructure, ai-agents, cli workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install release?

Run the command: npx killer-skills add jamesaphoenix/tx/release. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for release?

Key use cases include: ユースケース: Applying Use this skill when shipping a new tx version, ユースケース: Applying Run the local preflight:, ユースケース: Applying node scripts/release-preflight.mjs <version.

Which IDEs are compatible with release?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for release?

制約事項: Do not stop at tag creation. The release is not done until publish.yml succeeds.. 制約事項: Do not stop at tag creation. 制約事項: Requires repository-specific context from the skill documentation.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add jamesaphoenix/tx/release. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use release immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

release

# Release Use this skill when shipping a new tx version. It covers agent-infrastructure, ai-agents, cli workflows. This AI agent skill supports Claude Code

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Release

Use this skill when shipping a new tx version.

Default Flow

  1. Run the local preflight:
bash
1node scripts/release-preflight.mjs <version>
  1. Run the release gates:
bash
1bun run sync-readme
2bun run test:packages
3bunx eslint apps/ packages/ --max-warnings 0
4bun run typecheck
  1. Bump all workspace versions in lockstep:
  • package.json
  • packages/types/package.json
  • packages/core/package.json
  • packages/test-utils/package.json
  • packages/tx/package.json
  • apps/cli/package.json
  • apps/agent-sdk/package.json
  • apps/api-server/package.json
  • apps/mcp-server/package.json
  • apps/dashboard/package.json
  • apps/docs/package.json
  1. Commit, push, tag, and create the GitHub release.
  2. Watch publish.yml to completion.
  3. Verify npm registry versions for every published package.

In This Repo

  • publish workflow: .github/workflows/publish.yml
  • README sync: scripts/sync-readme.sh
  • preflight guardrail: scripts/release-preflight.mjs

Published packages:

  • @jamesaphoenix/tx-types
  • @jamesaphoenix/tx-core
  • @jamesaphoenix/tx-test-utils
  • @jamesaphoenix/tx
  • @jamesaphoenix/tx-agent-sdk
  • @jamesaphoenix/tx-api-server
  • @jamesaphoenix/tx-mcp-server
  • @jamesaphoenix/tx-cli

Rules

  • Always use a fresh version. If a publish failed, ship a new patch version.
  • Do not stop at tag creation. The release is not done until publish.yml succeeds.
  • Treat the workspace as lockstep versioned, including private apps.
  • Confirm npm moved, not just GitHub Actions.

Commands

bash
1node scripts/release-preflight.mjs <version>
2npm view @jamesaphoenix/tx version
3git commit -m "chore(release): <version>"
4git push origin main
5git tag v<version>
6git push origin v<version>
7gh release create v<version> --title "v<version>" --generate-notes
8gh run list --workflow publish.yml --limit 5
9gh run watch <run-id> --exit-status

Recovery

If publish fails:

  1. Inspect the failing step with gh run view.
  2. Fix the real issue locally.
  3. Re-run the release gates.
  4. Cut a fresh patch version.
  5. Optionally delete the stale failed GitHub release and tag if they should not stay visible.

関連スキル

Looking for an alternative to release or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

ローカライズされた概要: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
AI

nextjs-turbopack

[ 注目 ]
Logo of affaan-m
affaan-m

ローカライズされた概要: Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack. It covers ai-agents, anthropic, claude workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 169.5k
⑂ 0
生産性

widget-generator

Logo of f
f

ローカライズされた概要: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

ローカライズされた概要: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
ブラウザ