Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
Methodology for analyzing changes according to Semantic Versioning (SemVer) rules and determining the appropriate version number.
Install Semver Analyzer
$ npx skills add revfactory/harness-100 --skill semver-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 semver-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/39-changelog-generator/.claude/skills/semver-analyzer .claude/skills/semver-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "semver-analyzer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/39-changelog-generator/.claude/skills/semver-analyzer into .claude/skills/semver-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semver-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/revfactory/harness-100/tree/main/en/39-changelog-generator/.claude/skills/semver-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add revfactory/harness-100 --skill semver-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 semver-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/39-changelog-generator/.claude/skills/semver-analyzer .agents/skills/semver-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "semver-analyzer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/39-changelog-generator/.claude/skills/semver-analyzer into .agents/skills/semver-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semver-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill semver-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 semver-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/39-changelog-generator/.claude/skills/semver-analyzer .cursor/skills/semver-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "semver-analyzer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/39-changelog-generator/.claude/skills/semver-analyzer into .cursor/skills/semver-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semver-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/revfactory/harness-100.git --path en/39-changelog-generator/.claude/skills/semver-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add revfactory/harness-100 --skill semver-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 semver-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/39-changelog-generator/.claude/skills/semver-analyzer .gemini/skills/semver-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "semver-analyzer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/39-changelog-generator/.claude/skills/semver-analyzer into .gemini/skills/semver-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semver-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install revfactory/harness-100 semver-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add revfactory/harness-100 --skill semver-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/39-changelog-generator/.claude/skills/semver-analyzer .github/skills/semver-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "semver-analyzer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/39-changelog-generator/.claude/skills/semver-analyzer into .github/skills/semver-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semver-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill semver-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 semver-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/39-changelog-generator/.claude/skills/semver-analyzer .opencode/skills/semver-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "semver-analyzer" agent skill from https://github.com/revfactory/harness-100/tree/main/en/39-changelog-generator/.claude/skills/semver-analyzer into .opencode/skills/semver-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "semver-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
semver-analyzer- GitHub stars
- 1.3k
- Token cost
- ~978 tokens
- SKILL.md length
- 238 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Methodology for analyzing changes according to Semantic Versioning (SemVer) rules and determining the appropriate version number.
- SemVer analysis
- SKILL.md covers Target Agents, SemVer 2.0.0 Core Rules, Breaking Change Assessment… and Version Bump Decision Algorithm, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Version number determination
What it does
Semver Analyzer is an agent skill from revfactory/harness-100. Methodology for analyzing changes according to Semantic Versioning (SemVer) rules and determining the appropriate version number. Use this skill for 'SemVer analysis', 'version number determination', 'Breaking Change assessment', 'version bump decisions', and other version management tasks. Note: automatic git tag creation and CI/CD release execution are outside the scope of this skill.
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes and CI/CD. It works with Git. The licence is Apache-2.0.
When your agent uses it
- SemVer analysis
- Version number determination
- Breaking Change assessment
- Version bump decisions
Example prompts
- “SemVer analysis”
- “version number determination”
- “Breaking Change assessment”
- “/semver-analyzer”
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Semver Analyzer loads about 978 tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 238 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 238 words, ~978 tokens.
Download SKILL.mdSave it as
.claude/skills/semver-analyzer/SKILL.md (or your agent's skills folder).- name
- semver-analyzer
- description
- Methodology for analyzing changes according to Semantic Versioning (SemVer) rules and determining the appropriate version number. Use this skill for 'SemVer analysis', 'version number determination', 'Breaking Change assessment', 'version bump decisions', and other version management tasks. Note: automatic git tag creation and CI/CD release execution are outside the scope of this skill.
SemVer Analyzer — Semantic Versioning Analysis Methodology
A skill that enhances version determination capabilities for the change-classifier and release-note-writer.
Target Agents
- change-classifier — Determines the SemVer impact of changes
- release-note-writer — Determines version numbers and highlights
SemVer 2.0.0 Core Rules
MAJOR.MINOR.PATCH[-prerelease][+build]
MAJOR: Incompatible API changes (Breaking Change)
MINOR: Backward-compatible feature additions
PATCH: Backward-compatible bug fixesBreaking Change Assessment Matrix
API/Library
| Change Type | Breaking? | Example |
|---|---|---|
| Public function removed | YES | remove_user() deleted |
| Public function signature changed | YES | Required parameter added/removed |
| Return type changed | YES | dict to list |
| Exception type changed | YES | ValueError to TypeError |
| Default value changed | MAYBE | Depends on behavioral change |
| New optional parameter added | NO | def func(x, new=None) |
| New public function added | NO | No impact on existing code |
| Internal function changed | NO | _private_func() |
| Performance improvement | NO | Behavior unchanged |
Web API (REST/GraphQL)
| Change Type | Breaking? |
|---|---|
| Endpoint removed/moved | YES |
| Required field added (request) | YES |
| Response field removed | YES |
| Response structure changed | YES |
| Authentication method changed | YES |
| New optional field added (request) | NO |
| New response field added | NO |
| New endpoint added | NO |
Database
| Change Type | Breaking? |
|---|---|
| Table/column removed | YES |
| NOT NULL constraint added | YES |
| Column type changed | YES |
| New nullable column added | NO |
| New index added | NO |
Version Bump Decision Algorithm
Input: List of changes
1. Breaking Change present? -> MAJOR bump
2. New features present? -> MINOR bump
3. Bug fixes only? -> PATCH bump
Special rules:
- MAJOR = 0 (in development): Breaking Changes allowed as MINOR
- Pre-release versions: 0.x.y-alpha.1 -> MAJOR on stable release
- Mixed types: Apply the highest levelConventional Commits Mapping
| Prefix | SemVer Impact | Release Notes Section |
|---|---|---|
feat: | MINOR | Added |
fix: | PATCH | Fixed |
feat!: / BREAKING CHANGE: | MAJOR | Breaking Changes |
perf: | PATCH | Performance |
refactor: | - | Changed |
docs: | - | Documentation |
test: | - | - (may exclude from notes) |
chore: | - | - (may exclude from notes) |
ci: | - | - (may exclude from notes) |
style: | - | - (may exclude from notes) |
deps: | PATCH~MAJOR | Dependencies |
Keep a Changelog Format
# Changelog
## [Unreleased]
## [2.0.0] - 2025-01-15
### Breaking Changes
- `createUser()` API renamed to `registerUser()` (#123)
### Added
- Team management feature (#456)
- Dark mode support (#789)
### Changed
- Login screen UI improvements (#234)
### Deprecated
- `v1` API endpoints (will be removed in v3.0)
### Fixed
- Password reset email not sending (#567)
### Security
- XSS vulnerability patch (#890)Pre-Release Version System
1.0.0-alpha.1 -> Initial alpha
1.0.0-alpha.2 -> Alpha fix
1.0.0-beta.1 -> Beta entry
1.0.0-beta.2 -> Beta fix
1.0.0-rc.1 -> Release candidate
1.0.0 -> Stable release
Precedence: alpha < beta < rc < release© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/39-changelog-generator/.claude/skills/semver-analyzer of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Semver Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Semver Analyzer this skillrevfactory/harness-100 | 1.3k | — | ~978 | Automated safety check: Pass | Apache-2.0 | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 8.9k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Coffee GB Releasetrekawek/coffee-gb | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Kt Search Releasejillesvangurp/kt-search | 155 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Codex Proxy RS Releasezyycn/codex-proxy-rs | 738 | — | ~327 | Automated safety check: Pass | Apache-2.0 | |
| Docs CIjh941213/my-cc-harness | 126 | — | ~989 | Automated safety check: Notes | None |
Similar skills
Coffee GB Release
trekawek/coffee-gb
Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release.
Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
Codex Proxy RS Release
zyycn/codex-proxy-rs
Plans versions, writes release notes, publishes stable or pre-release builds and recovers from failed releases for Codex Proxy RS, without covering deploys or tag cleanup.
Docs CI
jh941213/my-cc-harness
Scaffold a docs-as-code CI/CD pipeline + docs drift detection — link check, OpenAPI lint/breaking gate, mermaid validation, docs freshness check, CHANGELOG automation, docs.yaml manifest.
Git Changes Reporter
No-Trade-No-Life/Yuan
生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。
More from revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Works with
Categories
Questions about Semver Analyzer
What does Semver Analyzer do?
Methodology for analyzing changes according to Semantic Versioning (SemVer) rules and determining the appropriate version number. Semver Analyzer is an agent skill from revfactory/harness-100. Methodology for analyzing changes according to Semantic Versioning (SemVer) rules and determining the appropriate version number.
When should I use Semver Analyzer?
Semver Analyzer fits situations like: semVer analysis; version number determination; breaking Change assessment; version bump decisions.
How do I install Semver Analyzer in Claude Code?
Run `npx skills add revfactory/harness-100 --skill semver-analyzer -a claude-code`. Or copy the skill folder (en/39-changelog-generator/.claude/skills/semver-analyzer in revfactory/harness-100) into .claude/skills/semver-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Semver Analyzer in Codex?
Run `npx skills add revfactory/harness-100 --skill semver-analyzer -a codex`. Or copy the skill folder (en/39-changelog-generator/.claude/skills/semver-analyzer in revfactory/harness-100) into .agents/skills/semver-analyzer in your project. Codex loads it when a task matches its description.
Can I use Semver Analyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add revfactory/harness-100 --skill semver-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/semver-analyzer, .gemini/skills/semver-analyzer, .github/skills/semver-analyzer and .opencode/skills/semver-analyzer in your project.
What does Semver Analyzer need to run?
SKILL.md names no scripts, command-line tools or credentials: Semver Analyzer is instructions for the agent only.
Does Semver Analyzer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Semver Analyzer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Semver Analyzer use?
Semver Analyzer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Semver Analyzer use?
About 978 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Semver Analyzer?
Skills that share tags, products or a category with Semver Analyzer: Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars), Coffee GB Release (trekawek/coffee-gb, 1.2k stars), Kt Search Release (jillesvangurp/kt-search, 155 stars) and Codex Proxy RS Release (zyycn/codex-proxy-rs, 738 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Semver Analyzer?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,290 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.