
tag-release
by vfarcic
Intelligent dual-mode agent for deploying applications to ANY Kubernetes cluster through dynamic discovery and plain English governance
SKILL.md
name: tag-release description: Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.
Create Release Tag
Create a semantic version tag based on accumulated changelog fragments. This aggregates all pending fragments to determine the appropriate version bump and creates an annotated tag.
When to Use
Run this skill when:
- Multiple PRs have been merged with changelog fragments
- You're ready to cut a release
- After the /prd-done workflow completes (not during it)
Workflow
Step 1: Check for Pending Fragments
List all files in changelog.d/ directory:
ls -la changelog.d/
If no fragments exist (only .gitkeep or empty), inform the user there's nothing to release.
Step 2: Get Current Version
Find the latest tag:
git tag --sort=-v:refname | head -1
If no tags exist, start from v0.0.0.
Step 3: Analyze Fragments for Version Bump
Examine all fragment files to determine the highest-impact change type:
Priority order: breaking > feature > bugfix > doc = misc
The highest-priority fragment type determines the version bump:
- Any
.breaking.mdexists → bump major (e.g., v1.2.3 → v2.0.0) - Any
.feature.mdexists → bump minor (e.g., v1.2.3 → v1.3.0) - Only
.bugfix.md,.doc.md, or.misc.md→ bump patch (e.g., v1.2.3 → v1.2.4)
Step 4: Propose Version
Show the user:
- Current version
- Fragments found (list them with their types)
- Proposed next version based on the analysis
- Ask for confirmation or allow override
Step 5: Create and Push Tag
If confirmed:
git tag -a [version] -m "[Brief description summarizing the fragments]"
git push origin [version]
Step 6: Confirm Success
Show the user:
- The tag created
- The tag URL on GitHub (if applicable)
- Note that CI/CD will generate release notes from the fragments
Guidelines
- Don't run during PR workflow: This is a separate release activity
- Review fragments first: Make sure all fragments are accurate before tagging
- Use semantic versioning: Follow semver strictly based on fragment types
- Brief tag message: Summarize the release in 1-2 sentences
Score
Total Score
Based on repository quality metrics
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
Reviews
Reviews coming soon