Results for “version-id”

Versioning exists because you cannot deploy your clients.

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.

Validates Claude Ads contracts, bundles, scores, runs, capabilities, repositories, and releases with deterministic checks and recovery steps.

Coordinate a full Galyarder Framework release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up.

Provides Git-like version control for ArcGIS web maps, wrapping the gitmap CLI to expose branch, commit, diff, push/pull, and map discovery as callable tools.

Designs system architecture, selects technology stack, creates ERDs and sequence diagrams, and records ADRs from BA artifacts, declaring a design freeze gate.

Runs an autonomous multi-agent software development pipeline that takes a PRD through to production with zero human intervention, using model-tiered agents, memory, and verification cycles.

Cut releases, validate changelogs, and manage git hooks for a project.

Check if the compound-engineering plugin is up to date and recommend the update command if not. Use when the user says "update compound engineering", "check compound engineering version", "ce update", "is compound engineering up to date", "update ce plugin", or reports issues that might stem from a stale compound-engineering plugin version. This skill only works in Claude Code — it relies on the plugin harness cache layout.

Updates StyleSeed engine files in a project by detecting the current setup, comparing versions, and safely applying additive updates without overwriting user code.