Results for “version”

Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches across nodes, planning upgrades, documenting cluster configuration, or troubleshooting version-related issues on HyperPod. Triggers on requests about versions, compatibility, component checks, or upgrade planning for HyperPod clusters.

The English summary is being prepared. Showing the original description.

Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.

The English summary is being prepared. Showing the original description.

Checks whether a new version of a repository preserves the behavior observed by tests on the old version. Use this skill when comparing two versions of code to detect regressions, verify refactoring safety, validate bug fixes don't break existing functionality, or ensure backward compatibility. Detects differences in function outputs, exceptions, observable states, and performance between versions. Generates reports highlighting potential regressions (critical, high, medium, low severity), improvements, and areas requiring verification. Triggers when users ask to check for regressions between versions, compare test behavior across versions, verify behavior preservation, or validate that changes don't break existing tests.

The English summary is being prepared. Showing the original description.

Release a new version of an R package including version bumping, NEWS.md updates, git tagging, GitHub release creation, and post-release development version setup. Use when a package is ready for a new patch, minor, or major release, after CRAN acceptance to create the corresponding GitHub release, or when setting up the development version bump immediately after a release.

The English summary is being prepared. Showing the original description.

Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST API rate limits, OpenAPI sObjects, API contract record, error contract, errorCode catalog, 410 GONE retired API version, HTTP 300 external ID upsert, idempotency key, deprecation notice, composite subrequest limit. NOT for building the endpoint or writing the Apex REST service — use apex/apex-rest-services. NOT for upgrading the API version on your own Apex, LWC or sfdx-project.json — use devops/api-version-management.

The English summary is being prepared. Showing the original description.

sparkle-design（公開 npm パッケージ）の新バージョンをリリースするための手順スキル。 package.json の version bump、CHANGELOG.md の更新、リリース PR 作成、PR マージ後の npm への stage、メンテナーによる 2FA 承認（npm stage approve）、承認後の git tag・ GitHub Release 作成までを一連の手順で実行する。 CHANGELOG 更新漏れと GitHub Release 作成漏れを防ぐためのチェックリストを含む。 「sparkle-design をリリース」「sparkle-design の新バージョンを切る」「vX.Y.Z をリリース」 「sparkle-design の CHANGELOG を更新」で発動。 English: "release sparkle-design", "cut a new sparkle-design version", "publish sparkle-design", "bump sparkle-design version".

The English summary is being prepared. Showing the original description.

Use when the user asks to "set up conversion values so tROAS optimizes profit not orders", "map margin onto my purchase value", "build value rules for lead / phone / signup conversions", or "stop bidding to revenue when I care about profit"; defines and QAs the conversion VALUE model — per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count sanity check — as a value-model spec plus a pre-launch value QA sheet. Not for whether the tag fires or UTMs are clean — use conversion-signal-qa; not for cross-platform double-count de-dup — use attribution-reconciler; not for scoring R1/R2 — that is a scored veto in ad-account-auditor. 付费广告转化价值建模/利润出价/价值规则QA

The English summary is being prepared. Showing the original description.

Manage semantic version updates for rad-mem project. Handles patch, minor, and major version increments following semantic versioning. Updates package.json, marketplace.json, plugin.json, and CLAUDE.md version number (NOT version history). Creates git tags and GitHub releases. Auto-generates CHANGELOG.md from releases.

The English summary is being prepared. Showing the original description.

Prepare code changes for sharing by merging the base branch, running tests, and reviewing the diff. Update VERSION and CHANGELOG, then commit, push, and create a pull request, a proposal to merge the changes.

• Create a pull request for completed work
• Test and review changes before pushing
• Merge the base branch before sharing changes

Review Storybook's minimum supported browser versions using Plausible documentation traffic data. The skill presents usage evidence and proposed versions for approval, then updates pinned settings and documentation and opens a pull request with the recorded decision.

• Review minimum browser versions using documentation traffic
• Compare browser version shares and approve support floors
• Update browser settings and migration documentation together

Find and read files in ChatGPT Library, save new deliverables, and update existing files while preserving their identity and version history. Organize folders, restore earlier versions, and manage sharing for Library files and folders.

• Find a Library file by name or content
• Summarize or compare saved documents
• Save a deliverable or update an existing file

Update Codex's pinned V8 and rusty_v8 versions, synchronize build settings and checksums, and validate a release candidate. If validation fails, investigate upstream changes and adjust the affected build files to restore a working build.

• Update Codex's pinned V8 and rusty_v8 versions
• Update prebuilt artifacts and checksums
• Validate a V8 release candidate

Find current documentation and code examples through the Context7 MCP server. Look up library setup, API usage, migration steps, and library-specific problems, using documentation for the requested version when available.

• Looking up documentation for a specific version
• Finding library setup and configuration steps
• Finding examples for code that uses external libraries

Review marketing pages and forms to identify obstacles to purchases, inquiries, or other desired actions. Get prioritized recommendations, alternative headlines and button text, and experiment ideas based on the page’s purpose and traffic sources.

• Reviewing a landing page with few conversions
• Improving plan comparisons on a pricing page
• Reducing contact form abandonment

Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.

• Updating Biome to a specified version
• Aligning configuration files after dependency updates
• Checking for issues introduced by a Biome update

Prepare a specified software version for release by checking version consistency and changelog readiness, building packages, and testing basic behavior. Produce checksums, release notes, and a readiness report; public release actions require separate authorization.

• Check version consistency and changelog readiness
• Build release packages and test basic behavior
• Prepare checksums and release notes

Manage NuGet packages, the libraries used by .NET projects, through consistent add, remove, and update procedures. Check that requested versions exist, locate their configuration, and run dependency restoration to check for errors after updates.

• Add a NuGet package to a .NET project
• Remove an unused package
• Update a package version across a solution

Migrate existing PowerShell Pester tests through major versions from v3 to v6. The skill guides assertion updates, setup restructuring, mock changes, and execution configuration, using before-and-after test results to investigate failures while preserving what each test checks.

• Migrating Pester tests one major version at a time
• Fixing tests broken by a Pester upgrade
• Updating legacy Should and Invoke-Pester syntax

Create and manage Arize datasets for evaluation and experiments using the ax CLI. Import records from files, append examples, inspect dataset versions, and export a chosen version for offline analysis, with checks for field consistency and export completeness.

• Creating evaluation datasets from files
• Adding examples to an existing test set
• Inspecting dataset metadata and versions

Analyze convertible bonds in China's A-share market through bond value, stock conversion value, and option value. Review conversion-price resets and redemption clauses, then compare candidates using low-price, low-premium screening and periodic portfolio rotation frameworks.

• Compare bond, stock conversion, and option values
• Review conversion-price resets and early redemption risks
• Screen bonds for low prices and low conversion premiums

Set up automated Android builds and Google Play publishing with GitHub Actions. Supports TWA, React Native, Flutter, and native Android, with signing setup, separate testing and production tracks, and automatic build-number increments on main.

• Setting up Google Play publishing from GitHub
• Separating internal, alpha, beta, and production releases
• Automating versionCode increments on main

Review marketing pages to find obstacles to signups, purchases, or inquiries. Assess headlines, action buttons, trust signals, and usability, then provide prioritized fixes, alternative wording, and hypotheses for comparing page versions through A/B tests.

• Finding reasons a landing page gets few signups
• Improving plan comparisons on a pricing page
• Matching page messaging to incoming ads

Test marketing prompts against shared cases, score required content, prohibited phrases, and output format, and compare alternatives. Keep version history and diffs, use reusable templates, and check that prompt or model updates preserve output quality.

• Compare two prompts for ads, email, or social content
• Keep prompt versions and review changes
• Check output quality after prompt or model updates

Plan, set up, audit, and debug analytics tracking with GA4 and Google Tag Manager. Define events and their parameters, configure conversion tracking, and investigate missing or duplicate data using structured checks and prioritized fixes.

• Building an event tracking plan from scratch
• Auditing existing tracking for gaps and duplicate events
• Debugging events missing from GA4