dot-ai-tag-release
Skill336 starsChanged 10 months agoMITView on GitHub
Create a release tag based on accumulated changelog fragments, then prune merged worktrees and branches. Run when ready to cut a release.
- Commits and pushes
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prds-getSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-decisionsSkill
- dot-ai-prd-update-progressSkill
- dot-ai-process-feature-requestSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- infographic-generatorSkill
- publish-mock-serverSkill
- write-docsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 12 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create a semantic version tag based on accumulated changelog fragments.
- Distinctive: line 13
Run this skill when:
- Distinctive: line 16
After the /prd-done workflow completes (not during it)
- Distinctive: line 22
Run the analysis script bundled with this skill:
- Very specific: line 27
If the script fails (non-zero exit) or the output contains ERROR=true, show the MESSAGE to the user and stop.
- Very specific: line 29
If the output contains NO_FRAGMENTS=true, inform the user there's nothing to release and stop.
- Distinctive: line 37
Ask for confirmation or allow override
- Very specific: line 41
If SKIP_CI=true, inform the user that tagging HEAD would prevent the release workflow from running.
- Very specific: line 71
If NOTHING_TO_CLEAN=true, tell the user there is nothing to clean and finish.
- Distinctive: line 79
After confirmation, process the items in this order:
- Distinctive: line 81
Remove each worktree (must come before deleting its branch — a branch checked out in a worktree cannot be deleted):
- Very specific: line 86
If a worktree has uncommitted changes git refuses.
- Distinctive: line 89
Delete each local branch:
- Very specific: line 93
Use -d (not -D) as a safety net — it refuses unmerged branches.
- Distinctive: line 96
Delete each remote branch:
- Distinctive: line 109
Review fragments first: Make sure all fragments are accurate before tagging
- Distinctive: line 112
Never tag [skip ci] commits: Always create a preparation commit first
- Distinctive: line 113
Clean up only after tagging: Run the cleanup step (Step 6) once the release is cut, never before — and always confirm the detected list …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Release Tag
Create a semantic version tag based on accumulated changelog fragments.
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: Analyze
Run the analysis script bundled with this skill:
bash .claude/skills/dot-ai-tag-release/analyze.shIf the script fails (non-zero exit) or the output contains ERROR=true, show the MESSAGE to the user and stop.
If the output contains NO_FRAGMENTS=true, inform the user there's nothing to release and stop.
Step 2: Propose Version
Present the script output to the user:
- Current version (
CURRENT_VERSION) - Fragments found (the
FRAGMENTSlist with their types) - Proposed next version (
PROPOSED_VERSION) based on bump type (BUMP_TYPE) - Ask for confirmation or allow override
Step 3: Handle [skip ci]
If SKIP_CI=true, inform the user that tagging HEAD would prevent the release workflow from running. Create a preparation commit:
git commit --allow-empty -m "chore: prepare release [version]"
git push origin HEADStep 4: Create and Push Tag
After confirmation:
git tag -a [version] -m "[Brief description summarizing the fragments]"
git push origin [version]Step 5: 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
Step 6: Clean Up Merged Worktrees and Branches
Once the release is tagged, the branches and worktrees whose work it contains are done. Run the read-only detection script bundled with this skill:
bash .claude/skills/dot-ai-tag-release/cleanup.shInterpret the output:
- If
NOTHING_TO_CLEAN=true, tell the user there is nothing to clean and finish. - Otherwise present the
WORKTREES,LOCAL_BRANCHES, andREMOTE_BRANCHESlists and ask the user to confirm before deleting anything.
This step is destructive — always show the full list and get explicit
confirmation first. Never touch the default branch (DEFAULT_BRANCH) or the
branch/worktree you are currently on; .claude/skills/dot-ai-tag-release/cleanup.sh already excludes them.
After confirmation, process the items in this order:
- Remove each worktree (must come before deleting its branch — a branch checked
out in a worktree cannot be deleted):
If a worktree has uncommitted changes git refuses; report it and skip rather than usinggit worktree remove [worktree_path]--force, unless the user explicitly asks. - Delete each local branch:
Usegit branch -d [branch]-d(not-D) as a safety net — it refuses unmerged branches. If it refuses, surface the warning and ask before forcing with-D. - Delete each remote branch:
git push origin --delete [branch]
Finally, prune stale worktree metadata:
git worktree pruneGuidelines
- 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. While the project is pre-1.0 (
v0.x), the minor digit is the compatibility boundary, sobreakingfragments bump the minor andfeature/bugfixfragments are patch releases; from1.0onward, standard semver applies (breaking→major,feature→minor,bugfix→patch). The.claude/skills/dot-ai-tag-release/analyze.shoutput already reflects this. - Brief tag message: Summarize the release in 1-2 sentences
- Never tag [skip ci] commits: Always create a preparation commit first
- Clean up only after tagging: Run the cleanup step (Step 6) once the release is cut, never before — and always confirm the detected list with the user, since removing worktrees and deleting branches is destructive
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

