Agent skill
semantic-release-tagger
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.
Install this agent skill to your Project
npx add-skill https://github.com/cskiro/claudex/tree/main/plugins/semantic-release-tagger/skills/semantic-release-tagger
SKILL.md
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:
- Auto-execute: Run git commands to gather context
- Present findings: Show detected conventions, latest versions, commits
- Recommend action: Calculate next version based on commits
- Confirm with user: "Create tag
component@X.Y.Z?" - Execute: Run git tag/push commands
- Verify: Show results and next steps
Workflow
| Phase | Description | Details |
|---|---|---|
| 0 | Auto-Context Analysis | → workflow/phase-0-auto-analysis.md |
| 1 | Choose Tag Convention | → workflow/phase-1-convention.md |
| 2 | Determine Version Number | → workflow/phase-2-version.md |
| 3 | Create Git Tags | → workflow/phase-3-create-tag.md |
| 4 | Create GitHub Release | → workflow/phase-4-github-release.md |
| 5 | Maintain Tag History | → workflow/phase-5-maintenance.md |
Quick Reference
Version Bump Rules
| Change Type | Example | Version Bump |
|---|---|---|
| BREAKING CHANGE | API removal | MAJOR (2.0.0) |
| feat: | New feature | MINOR (1.3.0) |
| fix: / chore: | Bug fix | PATCH (1.2.4) |
| First release | N/A | 0.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
- Best Practices
- Troubleshooting
Metadata
Category: release-management Source: Generated from 7 insights (docs/lessons-learned/version-control/)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
e2e-testing
Use PROACTIVELY when setting up end-to-end testing, debugging UI issues, creating visual regression suites, or automating browser testing. Uses Playwright with LLM-powered visual analysis, screenshot capture, and fix recommendations. Zero-setup for React, Next.js, Vue, Node.js, and static sites. Not for unit testing, API-only testing, or mobile native apps.
github-repo-setup
Use PROACTIVELY when user needs to create a new GitHub repository or set up a project with best practices. Automates repository creation with four modes - quick public repos (~30s), enterprise-grade with security and CI/CD (~120s), open-source community standards (~90s), and private team collaboration with governance (~90s). Not for existing repo configuration or GitHub Actions workflow debugging.
sub-agent-creator
Use PROACTIVELY when creating specialized Claude Code sub-agents for task delegation. Automates agent creation following Anthropic's official patterns with proper frontmatter, tool configuration, and system prompts. Generates domain-specific agents, proactive auto-triggering agents, and security-sensitive agents with limited tools. Not for modifying existing agents or general prompt engineering.
accessibility-audit
Use PROACTIVELY when user asks for accessibility review, a11y audit, WCAG compliance check, screen reader testing, keyboard navigation validation, or color contrast analysis. Audits React/TypeScript applications for WCAG 2.2 Level AA compliance with risk-based severity scoring. Includes MUI framework awareness to avoid false positives. Not for runtime accessibility testing in production, automated remediation, or non-React frameworks.
otel-monitoring-setup
Use PROACTIVELY when setting up OpenTelemetry monitoring for Claude Code usage tracking, cost analysis, or productivity metrics. Provides local PoC mode (full Docker stack with Grafana) and enterprise mode (centralized infrastructure). Configures telemetry collection, imports dashboards, and verifies data flow. Not for non-Claude telemetry or custom metric definitions.
json-outputs-implementer
Use PROACTIVELY when extracting structured data from text/images, classifying content, or formatting API responses with guaranteed schema compliance. Implements Anthropic's JSON outputs mode with Pydantic/Zod SDK integration. Covers schema design, validation, testing, and production optimization. Not for tool parameter validation or agentic workflows (use strict-tool-implementer instead).
Didn't find tool you were looking for?