Skip to content

Combine /version and /release into a single /deploy skill #36

@sebastientaggart

Description

@sebastientaggart

Currently the workflow requires two separate commands to go from a tagged version to a production release: /version (bump, tag, push) and then /release (create GitHub Release, promote branch). This adds friction and an extra step that can be forgotten.

The new /deploy skill combines both into a single command that:

  1. Checks current state (latest tag, commits since tag, open PRs)
  2. Optionally bumps the version (patch/minor/major) with user confirmation
  3. Creates the GitHub Release and, in multi-branch workflows, promotes the pre-production branch to main

This reduces the workflow from six commands to five and makes the deploy step self-contained.

Metadata

Metadata

Labels

enhancementNew feature or requestready-for-qaIssue is ready to be QA tested

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions