code releaser

Validate repository state and execute dx release commands with semantic versioning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/siteminder-au/claude-code-dx-plugin --skill code-releaser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code releaser
Source: https://github.com/siteminder-au/claude-code-dx-plugin/tree/main/skills/code-releaser
Command: npx skills add https://github.com/siteminder-au/claude-code-dx-plugin --skill code-releaser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @siteminder/dx, @anthropic-ai/claude-code.

What problem does it solve?

Manual code releases are prone to versioning errors and inconsistent tagging. This Skill automates the dx release command, ensuring semantic versioning and proper Git tagging without manual intervention, saving time and improving release quality.

Core Features & Use Cases

  • Semantic Versioning: Automatically increments major, minor, or patch versions based on user input or defaults, maintaining release consistency.
  • Git Integration: Fetches latest changes, checks tags, and ensures the correct branch for release, preventing common Git-related issues.
  • Workspace Validation: Verifies system paths and package.json presence before release, ensuring a valid release environment.
  • Use Case: Ready to push a new minor version of channels-plus? Simply ask "make a minor code release for channels-plus" and the Skill handles the versioning and tagging, streamlining your release pipeline.

Quick Start

make a minor code release for channels-plus

Frequently Asked Questions about code releaser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code releases with semantic versioning?

Automate code releases by running the dx release command through this Skill, which validates your repository, increments versions (major, minor, or patch) automatically, applies Git tags, and executes the release without manual versioning errors. Requires a root package.json and correct branch alignment.

What does semantic versioning mean for CI/CD pipelines?

Semantic versioning is a versioning scheme (major.minor.patch) that signals breaking changes, new features, and bug fixes. This Skill enforces it during releases to ensure consistent version increments across your CI/CD pipeline and prevent versioning conflicts.

Can I automate Git tagging and version bumps in one step?

Yes. This Skill combines Git tag discovery, version increment calculation, and dx release execution in a single command, eliminating separate manual steps and reducing the risk of misaligned tags or version numbers.

What do I need to set up before making a code release?

Ensure your project has a root package.json, correct system and systemPath configuration, and your working branch is aligned with master. The Skill validates these prerequisites before proceeding with the release.

Why should I use automation for releases instead of manual commands?

Manual releases are error-prone and inconsistent. Automation prevents versioning mistakes, enforces semantic versioning rules, ensures proper Git tagging, and streamlines your release pipeline by eliminating repetitive steps.

Does this Skill work with projects that don't use package.json?

No. This Skill requires a root package.json file to function. Projects without one cannot use this automation and must handle releases manually or through alternative tools.