AgentSkillsCN

semantic-release-tagger

当您需要在 PR 合并到 main 后创建发布版本,或当用户询问版本管理策略时,可主动使用此技能。该技能是一款自动化的 git 标签生成器,能够分析仓库状态、解析常规提交信息,计算语义版本,并结合 GitHub Releases 生成带注释的 git 标签。它还支持以 @ 分隔符约定命名的单体仓库命名空间标签。此技能不适用于生成变更日志,也不适用于预发布或 Alpha 版本的管理。

SKILL.md
--- frontmatter
name: semantic-release-tagger
description: Use PROACTIVELY when creating releases after PR merges to main, or when user asks about versioning strategy. Automated git tagging agent that analyzes repository state, parses conventional commits, calculates semantic versions, and creates annotated git tags with GitHub releases. Supports monorepo namespaced tags with @ separator convention. Not for changelog generation or pre-release/alpha versioning.

Semantic Release Tagger

Overview

This skill is an interactive automation agent that handles the complete git tagging workflow. It analyzes your repository state, detects existing conventions, parses conventional commits to determine version bumps, and executes tag creation commands with your confirmation.

Key Capabilities:

  • Auto-analyze repository context: Detect existing tags, conventions, and monorepo structure
  • Intelligent version calculation: Parse conventional commits (feat/fix/BREAKING) to determine MAJOR.MINOR.PATCH bumps
  • Automated tag creation: Execute git commands after user confirmation
  • GitHub release integration: Optional release creation with auto-generated changelog
  • Monorepo awareness: Component-specific versioning with namespace support

When to Use This Skill

Trigger Phrases:

  • "how should I tag this release?"
  • "version this component"
  • "create semantic git tags"
  • "The PR was merged, create a release"

Use PROACTIVELY when:

  • User is about to create a release or tag
  • User asks about versioning strategy
  • User mentions monorepo or multi-component versioning

Do NOT use when:

  • User wants to create a branch (not a tag)
  • User is working with version numbers in code (package.json)
  • User needs changelog generation (use release-management skill)

Response Style

Interactive Automation Agent: Automatically analyze repository state, present findings with recommendations, get user confirmation, then execute commands.

Execution Pattern:

  1. Auto-execute: Run git commands to gather context
  2. Present findings: Show detected conventions, latest versions, commits
  3. Recommend action: Calculate next version based on commits
  4. Confirm with user: "Create tag component@X.Y.Z?"
  5. Execute: Run git tag/push commands
  6. Verify: Show results and next steps

Workflow

PhaseDescriptionDetails
0Auto-Context Analysisworkflow/phase-0-auto-analysis.md
1Choose Tag Conventionworkflow/phase-1-convention.md
2Determine Version Numberworkflow/phase-2-version.md
3Create Git Tagsworkflow/phase-3-create-tag.md
4Create GitHub Releaseworkflow/phase-4-github-release.md
5Maintain Tag Historyworkflow/phase-5-maintenance.md

Quick Reference

Version Bump Rules

Change TypeExampleVersion Bump
BREAKING CHANGEAPI removalMAJOR (2.0.0)
feat:New featureMINOR (1.3.0)
fix: / chore:Bug fixPATCH (1.2.4)
First releaseN/A0.1.0

Tag Convention Options

  • NPM-style @ (recommended): marketplace@1.0.0
  • Slash-based: marketplace/v1.0.0
  • Flat: v1.0.0 (single component only)

Reference Materials

Metadata

Category: release-management Source: Generated from 7 insights (docs/lessons-learned/version-control/)