Results for “system-versioning”

Semantic versioning releases — version bumps, changelogs, tags, publishing. Use when preparing a new release: deciding the version bump, drafting the changelog, tagging the commit, and publishing to the project's distribution channel.

Define version control strategies for design files, component libraries, and design assets to enable team collaboration and consistency.

Manages semantic versioning and changelog documentation for Flutter projects, defining a structured process for recording additions, changes, and removals across backend and mobile releases.

Versioning exists because you cannot deploy your clients.

ML pipeline design — data versioning, experiment tracking, deployment patterns, drift monitoring. Use when building an ML pipeline from data to deployment, setting up MLOps tooling (DVC, MLflow, model registry), choosing deployment patterns (shadow, canary, A/B), or designing monitoring for drift and degradation.

Optimizes hot-path scalar loops in .NET 8+ with cross-platform Vector128/Vector256/Vector512 SIMD intrinsics, or replaces manual math loops with single TensorPrimitives API calls.

Data Version Control for ML projects. Track large datasets and models alongside Git, build reproducible ML pipelines, and run experiments with metric comparison. Works with any storage backend including S3, GCS, Azure, and local filesystems.

Structures git workflow practices for committing, branching, resolving conflicts, and organizing work across multiple parallel streams.

Run any Replicate model (image gen, audio, video) by version ID

Automates semantic versioning and release workflow for Claude Code plugins, including version increments across multiple manifest files, build verification, git tagging, GitHub releases, and changelog generation.

Documents, standardizes, and governs a Vue 3 + shadcn-vue design system, including component documentation templates, patterns for forms, empty states, loading states, and feedback, plus a consistency checklist and conventional commit conventions.

Version bump, generate changelog, tag, and prepare a release

Begins a new version release using git-flow. This skill should be used when the user asks to "start a release", "create release branch", "prepare a release", "git flow release start", or wants to begin a new version release. Accepts either an explicit version or a natural-language description of the release.

Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.

Best practices for MariaDB system-versioned (temporal) tables, covering creation, querying historical data, managing history growth, and handling ALTER TABLE operations.

Manage Git repositories and collaborative workflows — branching strategies, commit hygiene, conflict resolution, pull requests, hooks, and .gitignore management. Use when the user requests version control or provides relevant inputs for this workflow.

Identify, test, deploy, and verify software updates across an organization's IT infrastructure using a structured patch management workflow with phased rollouts and automated assessment.

Deploy a trained model to serving with versioning, shadow or canary rollout, and a tested rollback path.

Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, a host installer, or a community package), when a user wants to draft a migration plan, when an agent needs to reason about pending migrations, or when working through an in-progress migration.

Create, execute, and roll back versioned database schema migrations using tools like Alembic, Prisma Migrate, Flyway, and Knex. Use when the user requests database migration or provides relevant inputs for this workflow.

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

MVCC (Multi-Version Concurrency Control)

Cross-repository dependency audit. Scans package manifests for outdated packages, security advisories, version conflicts, and license issues. Produces a prioritized update plan. Supports Node.js, Python, Rust, and Go projects.

Production-quality Bash scripts for Solana vanity generation, keypair verification, batch operations, dependency auditing, and test orchestration — with security-hardened patterns including file permissions, input validation, and cleanup traps.

A git SHA pins the transformation.

`analysis-agent`/`task-agent`/`review-agent`: use when API, schema, event, or behavior changes need compatibility, deprecation, rollout, or migration; skip without version impact.

Manage version bumper operations. Auto-activating skill for DevOps Basics. Triggers on: version bumper, version bumper Part of the DevOps Basics skill category. Use when working with version bumper functionality. Trigger with phrases like "version bumper", "version bumper", "version".

Streams live training metrics, system stats, and gradients from active W&B runs, alerts on metric regressions, and posts summaries to Slack.

Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.

Manage tool versions and tasks with mise (formerly rtx). Use when a user asks to manage Node.js/Python/Go versions per project, replace nvm/pyenv/asdf, or define project-level tool requirements.

Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Use this proactively, without waiting to be asked, whenever evaluating a new feature, a layout, a section, a visual, a design, or any UI decision — divergent options beat a single guess. Fast, no interview, single-component scope. For a full structured exploration (interview, 5 variants of a whole page, real feedback collection, implementation plan) when the direction itself is still open, use `design-lab` instead — that one requires explicit invocation. Source: github.com/emilkowalski/skills.

Upgrades PowerShell Pester test suites across major versions (v3→v4, v4→v5, v5→v6) with structured workflows, reference guides, and safety rules.

Agent Vault — fetching secrets from Infisical at runtime