skills.rest
Conceptual-Machines
Conceptual-MachinesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release

Create and push a v-prefixed git tag on the main branch.

195|21|Updated Jan 17, 2026
Search Tags:#git#workflow#versioning#release#tagging#ci
One-click install
npx skills add https://github.com/Conceptual-Machines/magda-core --skill release-conceptual-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Conceptual-Machines/magda-core/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Conceptual-Machines/magda-core --skill release-conceptual-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tag the current main with a release version to create a reproducible, auditable snapshot without merging feature branches, simplifying release management.

Core Features & Use Cases

  • Tag-only releases on main to preserve a clean history for versioned software.
  • Works with CI that publishes artifacts, changelogs, and deployments from the tagged commit.
  • Provides guardrails: requires on-main, up-to-date before tagging and enforces a v-prefixed tag naming convention.

Quick Start

Tag the current main with the provided version (e.g., v1.2.3) and push the new tag to origin.

Frequently Asked Questions about release

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

FAQPage Schema
How do I tag a release on the main branch without merging feature branches?▼

To tag a release without merging, you create a git tag directly on the main branch. This provides a reproducible, auditable snapshot of your codebase while preserving a clean project history.

What's the best way to automate versioning and artifact publishing in a git workflow?▼

Git workflow automation for versioning uses tag-only releases on main to trigger CI pipelines. The pipeline detects the pushed tag to automatically publish artifacts, generate changelogs, and handle deployments.

Does a git tag release process require the main branch to be up-to-date?▼

Yes, git tag release processes require the main branch to be up-to-date. Enforcing prerequisites ensures your local main branch matches origin before tagging, maintaining reproducible and auditable release snapshots.

How do I enforce a v-prefixed naming convention for git release tags?▼

Enforcing a v-prefixed naming convention for git release tags requires applying explicit guardrails during the tagging step. This ensures version numbers like v1.2.3 are consistently formatted before pushing to origin.

Can I use a tag-only release strategy with my existing CI pipelines?▼

Yes, you can use a tag-only release strategy with existing CI pipelines. This approach works seamlessly with CI that publishes artifacts and generates changelogs directly from the tagged commit.

Why use a git tag for releases instead of merging a release branch?▼

Using a git tag for releases avoids the complexity of merging release branches. It creates an auditable snapshot on main, simplifying release management while keeping your project history completely clean.

Related Skills

Explore More Software Engineering Skills→
webdevcodywebdevcody
22

commit-push-and-release

Commit and push working-tree changes on main, then cut and push a minor version release tag.

Community
Intermediate
whilpwhilp
9

gh-workflow

Trigger and monitor GitHub Actions workflows via gh CLI.

Community
Advanced
hrygohrygo
47

hotplex-release

Automate HotPlex releases with version bumps, changelogs, and unified component versions.

Community
Advanced
Pixley-GrowthPixley-Growth
3

hotfix-done

Merge hotfix to main and feature branches, tag release, and clean up.

Official
Advanced