「release」の検索結果

Reference for RIPDPI release signing config and versioning. Use when touching signing config or version bumps. Keep rules: r8-jni-keep-rules. Tagging and publishing: ripdpi-release.

日本語の概要は準備中です。原文の説明を表示しています。

Explicit request only -- never invoke implicitly, never expose signing secrets. Prepares and publishes one exact-SHA RIPDPI release via the release contract. Use when asked to prepare or publish a version.

日本語の概要は準備中です。原文の説明を表示しています。

Validates and summarizes the four required authorization forms in a personal injury matter (retainer, HIPAA release, insurance authorization, employment record release). Confirms signatures, dates, scope, and completeness to determine readiness for the investigation phase. Use when reviewing client onboarding packets, verifying authorization forms before discovery, or checking HIPAA and record-release compliance.

日本語の概要は準備中です。原文の説明を表示しています。

Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".

日本語の概要は準備中です。原文の説明を表示しています。

Audit skillsaw for release readiness — test new rules against real repositories, audit core architectural dimensions, independently verify proposed fixes, and ship improvements in clean, focused batches. Use before cutting a release.

日本語の概要は準備中です。原文の説明を表示しています。

Configures CI/CD pipelines for automated Python package publishing to PyPI or GitLab Package Registry. Use when creating GitHub Actions or GitLab CI release workflows, setting up trusted publishing or API token-based PyPI authentication, configuring version management with git tags and hatch-vcs, writing pyproject.toml publishing metadata, testing packages against TestPyPI, or documenting the release process for a Python project.

日本語の概要は準備中です。原文の説明を表示しています。

Agent skill for release-swarm - invoke with $agent-release-swarm

日本語の概要は準備中です。原文の説明を表示しています。

Prepare Anarlog Nightly builds and promote tested desktop stable versions with current CLI, local and hosted MCP, API, agent packages, and documentation. Deploy any required hosted services during the release. Validate and merge release updates before publishing. Distribute mobile builds when requested.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Bump, validate, publish, and announce a public @bex-co/bex-security release using upstreamVersion-bex.N. Use only when explicitly asked to cut or publish a Bex Security release.

日本語の概要は準備中です。原文の説明を表示しています。

Updates tdmcp docs and roadmap for newly shipped or newly merged capabilities. Use when asked to update docs, update the roadmap, reconcile release docs, document new features, sync docs with CHANGELOG/package release, refresh cookbook examples after a feature wave, re-run/continue/fix a docs-roadmap pass, or check whether docs/ROADMAP.md is current. Runs a sub-agent workflow: release audit -> roadmap/docs edit + cookbook sync -> QA.

日本語の概要は準備中です。原文の説明を表示しています。

Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.

日本語の概要は準備中です。原文の説明を表示しています。

当用户明确要求发布项目到 GitHub、创建 GitHub Release 或生成 Release Notes 时使用。根据版本历史整理发布说明；仅要求预览时不执行发布。

日本語の概要は準備中です。原文の説明を表示しています。

Authoritative reference for working with the released Wandelbots NOVA API v2 in the wandelbots-nova Python SDK. Use whenever a task touches the NOVA API, the generated `wandelbots_api_client` models (`nova.api.models.*`), motion planning requests (`plan_trajectory`, `MotionGroupSetup`, `LimitSet`, `LimitsOverride`), robot limits, or torque/velocity/acceleration/jerk limits. Reach for this skill before guessing field names or assuming a field exists — the installed client reflects the RELEASED API, while nightly specs may contain unreleased fields. Especially relevant for controller-reported limits (e.g. KUKA torque) and any "does field X exist / how is it forwarded to the planner?" question.

日本語の概要は準備中です。原文の説明を表示しています。

Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.

日本語の概要は準備中です。原文の説明を表示しています。

Package source files into plugin directories using release-mapping.yaml. Use when preparing a plugin release.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain a changelog following Keep a Changelog format. Covers entry categorization (Added, Changed, Deprecated, Removed, Fixed, Security), version section management, and unreleased tracking. Use when starting a new project that needs a changelog, adding entries after completing features or fixes, preparing a release by promoting Unreleased entries to a versioned section, or converting a free-form changelog to Keep a Changelog format.

日本語の概要は準備中です。原文の説明を表示しています。

Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes before tagging, evaluating whether a change constitutes a breaking change, adding pre-release identifiers, or resolving disagreement about what version bump is appropriate.

日本語の概要は準備中です。原文の説明を表示しています。

Audit an already completed protected Proto UI publication and reconcile immutable external facts with Version entities, release records, and public projections. Use after publication for registry, tag, GitHub Release, asset, checksum, workflow-head, and deployment evidence. Never republish or replace immutable evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Define release scope and move backlog workstreams between release targets.

日本語の概要は準備中です。原文の説明を表示しています。

Grafema release procedure for publishing new versions to npm. Covers happy path, pitfalls, rfdb binary lifecycle, and rollback. Use when user says "release", "publish", "bump version".

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrates the full powerball-harness plugin release with build, validation, version bump, CHANGELOG, tag, and GitHub Release. Use when releasing this plugin.

日本語の概要は準備中です。原文の説明を表示しています。

Evolution CMS JP Edition のリリース作業を対話形式でガイドするスキル。バージョン更新・タグ作成・GitHub Actions によるパッケージビルドまでを順を追って進める。「リリース」「release」と依頼されたときに使用する。

Release a NowStack Mobile Android app to Google Play production - listing, screenshots, Data safety, content rating, release notes, then promote the tested internal build to the production track with a staged rollout. Use for "release on Android", "publish to Play production", "promote to production", "ship the Android update". If no build is on a testing track yet, run ns-android-beta first.

日本語の概要は準備中です。原文の説明を表示しています。