「semver」の検索結果

Syncpack (モノレポ依存バージョン同期ツール) リファレンス。 .syncpackrc 設定、lint / fix / update / format コマンド、 versionGroups, semverGroups, updateGroups, customTypes, source, catalog プロトコル, semverRangeOnly, minimumReleaseAge, severity, sourceMode, package.json 整列、依存バージョン揃え、CI 連携。

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.

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

Package management discipline for any JavaScript/TypeScript project: dependency declaration, semver, scripts conventions, lockfile hygiene, package-manager detection (npm/yarn/pnpm). Stack-agnostic — referenced by every JS/TS framework plugin in the marketplace. Use this skill to: - Add a dependency correctly (right field, right semver range). - Pick the project's package manager from lockfile. - Define `scripts` entries that match conventions. - Avoid lockfile mistakes (manual edits, wrong commits). Do NOT use this skill for: - Code-level conventions (see the active framework plugin's conventions skill). - Framework-specific package patterns (NestJS modules, Angular schematics, Expo SDK choice etc.).

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

xp-harness の version を上げて GitHub Release を作る開発者向け skill。現バージョン確認 → 次バージョン判定 (semver) → 変更内容のユーザー向け / 開発者向け分類 → tag + push → gh release create までの流れを定義。「リリースする」「タグを打つ」「v0.x.x をリリース」と明示されたときに発火。

リリース単位（単一パッケージか monorepo か）を判定し，SemVer でバージョンを上げ（マニフェストと全参照箇所を整合），bump コミット・タグ・push・About 欄・GitHub Release までの文面を提案．承認後に一気に実行する．「リリースして」「公開して」「バージョンを上げて」など版を公にすることを求められたときに使う．記録するだけなら /capstone:commit を使う．

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major|explicit-semver>. Triggers: publish, release, deploy, npm publish.

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

Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.

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

Prepare and cut one signed NemoClaw semver release tag, then follow release workflows and draft the Announcement.

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

Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22

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

Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents

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

Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "release prep", "bump and PR", "open release PR", "what kind of release do we need", or any phrasing that ends in opening a release PR -- even when the user does not say "skill". Stops BEFORE tagging; tagging stays a human gate that triggers the release workflow. Refuses to bump to a major (>= 1.0.0) version without explicit operator confirmation.

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

Govern how the design system evolves — SemVer for tokens/components, the contribution workflow, deprecation policy, and change communication. Use when the user wants to add/promote/deprecate a component or token, decide a version bump, set up a contribution process, or keep the system from fragmenting.

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

Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.

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

When you want to create, adapt, or update an Agent Skill (Claude Code, Codex, Cursor, and other hosts) in one of your repos (listed in ~/.config/makerskills/skillify/repos.yaml; defaults to makerskills). Modes — CREATE (from chat, video, dump, or scratch) turns a workflow into a new skill. ADAPT ports an external skill with keep/adapt/add classification, license check, and attribution. UPDATE improves existing skills from learnings with cross-skill propagation, memory-vs-skill triage, and semver. Checks new skills for host portability. Triggers on "/skillify," "create a skill," "make this a skill," "skill from this chat," "adapt this skill," "port this skill," "fork this skill," "update X skill," "apply this to the relevant skills," "propagate this learning," "improve [skill]," "fix [skill]." Part of the -ify trifecta (skillify / toolify / loopify).

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

Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.

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

Dependency upgrades: outdated/vulnerable deps planned into semver waves (patch/minor batched, majors gated and changelog-read), applied incrementally with lockfiles regenerated and tests green after each. Runs on green main. Triggers on "absolute upgrade", "upgrade our dependencies", "bump deps", "update packages", "move off the deprecated X", "clear the Dependabot backlog".

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

Scaffold and amend the L1 Investment Constitution — [ALL_CAPS] placeholder bootstrap, SemVer bump rules, Sync Impact Report, MINOR/MAJOR re-examination dispatch after the gate-5 budget confirm. Thesis creation stays refused until ratification (Q83).

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

Cut a new TMDb release — work out the next SemVer version from the evidence, do the pre-tag housekeeping a tag would otherwise freeze in place, draft release notes, then tag and publish the GitHub release. Presents the version (with its reasoning) and the full notes for approval and STOPS; nothing is tagged or published until you say go.

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

Autonomously cut a Rove (`@sma1lboy/rove`) release end-to-end — detect the semver bump from pending changesets (flagging an upstream `minor` you didn't intend), run the release gates, dispatch the Changesets workflow (or run `scripts/release.sh` locally), then poll the GitHub Actions Release workflow with `gh` until npm publish completes, diagnosing CI failures (npm token, registry 404, lint, branch mismatch) instead of leaving them silent. Use when the user says "cut a release", "ship a version", "release Rove", "release rove", "发版", "release.sh", or "bump the version". Never force-pushes; always verifies the release landed on `main`.

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

Audit project dependencies for outdated packages, security vulnerabilities, and breaking changes. Use when someone asks to "check for outdated packages", "audit dependencies", "find vulnerable dependencies", "plan dependency upgrades", "detect breaking changes", or "update npm packages safely". Analyzes package.json/lock files, cross-references changelogs, and produces ordered upgrade plans.

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

Assists with managing versioning and changelogs in JavaScript/TypeScript monorepos using Changesets. Use when automating semantic versioning, generating changelogs from PRs, coordinating multi-package releases, or publishing to npm. Trigger words: changesets, versioning, changelog, npm publish, monorepo release, semver.

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

Cut a paad release — pick the semver bump from what is in [Unreleased], run make release, merge, tag, and verify the published plugin

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

Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels. Use when asked to "design a deprecation policy", "how should we version the API", or "set a sunset timeline".

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

Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates. Use when asked to "define an API stability policy", "set our deprecation timeline", or "write semver rules".

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