npx skills add https://github.com/alienfast/claude --skill 'Semantic Version Advisor'此技能帮助分类版本变更、确定适当的版本升级并验证语义化版本决策。
版本格式 : MAJOR.MINOR.PATCH
输入 : 旧版本和新版本 输出 : 分类(MAJOR/MINOR/PATCH)及解释
┌─────────────────────────────────┐
│ 比较版本 X.Y.Z │
└────────────┬────────────────────┘
│
v
┌────────────────┐
│ X 改变了吗? │─ 是 ──> MAJOR(破坏性变更)
└────┬───────────┘
│ 否
v
┌────────────────┐
│ Y 改变了吗? │─ 是 ──> MINOR(新功能)
└────┬───────────┘
│ 否
v
┌────────────────┐
│ Z 改变了吗? │─ 是 ──> PATCH(错误修复)
└────┬───────────┘
│ 否
v
版本相同
MAJOR.MINOR.PATCH^、~、>= 等前缀(如果存在)^4.0.0 → ^5.0.0 = MAJOR (4 → 5, 破坏性变更)
^13.1.5 → ^13.2.0 = MINOR (1 → 2, 新功能)
^7.1.5 → ^7.1.6 = PATCH (5 → 6, 错误修复)
9.35.0 → 9.36.0 = MINOR (35 → 36, 新功能)
1.0.0 → 1.0.1 = PATCH (0 → 1, 错误修复)
输入 : 发布中包含的变更列表 输出 : 推荐的版本升级(MAJOR/MINOR/PATCH)
需要 MAJOR 升级,如果存在以下任意情况 :
需要 MINOR 升级,如果存在以下任意情况 :
PATCH 升级,如果满足以下所有条件 :
从 PATCH 开始(默认)
↓
对于每个变更:
- 是破坏性变更吗? → 升级到 MAJOR,停止
- 是新功能吗? → 升级到 MINOR,继续
- 是错误修复吗? → 保持当前级别,继续
↓
返回遇到的最高级别
变更列表 :
getData() 中的空指针异常fetchAsync() 方法分析 :
结果 : MINOR 升级(添加了新功能)
输入 : 当前版本、提议版本、变更列表 输出 : 验证结果(有效/无效)及原因
1.5.3 → 2.0.0 ✅(MINOR 和 PATCH 重置)1.5.3 → 1.6.0 ✅(PATCH 重置)1.5.3 → 1.5.4 ✅(无需重置)有效 :
1.2.3 → 2.0.0 包含破坏性变更 ✅1.2.3 → 1.3.0 包含新功能 ✅1.2.3 → 1.2.4 包含错误修复 ✅无效 :
1.2.3 → 1.4.0(跳过 MINOR 版本) ❌1.2.3 → 2.1.0(MINOR 未重置为 0) ❌1.2.3 → 1.2.3(无变更) ❌1.2.3 → 1.3.0 包含破坏性变更(版本过低) ❌1.2.3 → 2.0.0 仅包含错误修复(版本过高) ❌错误 : ^7.1.5 → ^7.1.6 = "Major",因为存在脱字符 正确 : ^7.1.5 → ^7.1.6 = PATCH(忽略 ^,比较数字)
错误 : 核心包变更 → 必须是 MAJOR 正确 : 根据版本号分类,而非包的重要性
错误 : 1.5.3 → 2.1.0 作为 MAJOR 升级 正确 : 1.5.3 → 2.0.0 作为 MAJOR 升级(重置 MINOR 和 PATCH)
错误 : 安全修复 → 必须是 PATCH 正确 : 安全修复可以是任何级别(破坏性修复 = MAJOR)
1.0.0-alpha.1 - Alpha 预发布1.0.0-beta.2 - Beta 预发布1.0.0-rc.1 - 发布候选1.0.0-alpha.1
< 1.0.0-alpha.beta
< 1.0.0-beta
< 1.0.0-beta.2
< 1.0.0-rc.1
< 1.0.0
1.0.0 → 1.0.0-alpha.1 = 预发布(无语义化版本升级)1.0.0-beta.1 → 1.0.0 = 正式发布(无语义化版本变更)1.0.0-rc.1 → 1.1.0 = 从 RC 到 MINOR 发布所需研究 :
时间投入 : 高(30-60 分钟)
所需研究 :
时间投入 : 中等(10-20 分钟)
所需研究 :
时间投入 : 低(2-5 分钟)
# 查看过时包及其版本信息
npm outdated
# 机器可读的升级信息
npx ncu --jsonUpgraded
# pnpm 版本检查
pnpm outdated
# 分类版本差异
semver diff 1.2.3 1.3.0 # 输出: "minor"
# 比较版本
semver gt 1.3.0 1.2.3 # 输出: true
# 检查范围满足情况
semver satisfies 1.2.4 "^1.2.3" # 输出: true
**推荐版本升级**: [MAJOR/MINOR/PATCH]
**当前版本**: X.Y.Z
**提议版本**: A.B.C
**变更摘要**:
- [破坏性/功能/修复]: 描述
**原因**:
[根据变更类型解释此分类的原因]
**迁移说明**(如果是 MAJOR):
[消费者所需的步骤]
**包**: package-name
**版本变更**: X.Y.Z → A.B.C
**分类**: [MAJOR/MINOR/PATCH]
**影响评估**:
- 破坏性变更: [是/否]
- 新功能: [是/否]
- 安全修复: [是/否]
**推荐操作**: [立即更新/先测试/仔细审查]
| 旧版本 | 新版本 | 变更类型 | 分类 |
|---|---|---|---|
| 1.2.3 | 2.0.0 | X 改变 | MAJOR |
| 1.2.3 | 1.3.0 | Y 改变 | MINOR |
| 1.2.3 | 1.2.4 | Z 改变 | PATCH |
| ^4.0.0 | ^5.0.0 | X 改变 | MAJOR |
| ~1.2.3 | ~1.3.0 | Y 改变 | MINOR |
| 9.35.0 | 9.36.0 | Y 改变 | MINOR |
| 0.2.3 | 0.3.0 | Y 改变 | MINOR (0.x) |
有关完整的语义化版本规则和标准,请参阅:~/.claude/standards/semver.md
每周安装数
0
仓库
首次出现
1970年1月1日
安全审计
This skill helps classify version changes, determine appropriate version bumps, and validate semantic versioning decisions.
Version Format : MAJOR.MINOR.PATCH
Input : Old version and new version Output : Classification (MAJOR/MINOR/PATCH) with explanation
┌─────────────────────────────────┐
│ Compare versions X.Y.Z │
└────────────┬────────────────────┘
│
v
┌────────────────┐
│ X changed? │─ YES ──> MAJOR (breaking changes)
└────┬───────────┘
│ NO
v
┌────────────────┐
│ Y changed? │─ YES ──> MINOR (new features)
└────┬───────────┘
│ NO
v
┌────────────────┐
│ Z changed? │─ YES ──> PATCH (bug fixes)
└────┬───────────┘
│ NO
v
Same version
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
MAJOR.MINOR.PATCH from both versions^, ~, >= prefixes if present^4.0.0 → ^5.0.0 = MAJOR (4 → 5, breaking changes)
^13.1.5 → ^13.2.0 = MINOR (1 → 2, new features)
^7.1.5 → ^7.1.6 = PATCH (5 → 6, bug fixes)
9.35.0 → 9.36.0 = MINOR (35 → 36, new features)
1.0.0 → 1.0.1 = PATCH (0 → 1, bug fixes)
Input : List of changes to be included in release Output : Recommended version bump (MAJOR/MINOR/PATCH)
MAJOR bump required if ANY of :
MINOR bump required if ANY of :
PATCH bump if ALL of :
Start with PATCH (default)
↓
For each change:
- Breaking change? → Upgrade to MAJOR, stop
- New feature? → Upgrade to MINOR, continue
- Bug fix? → Keep current level, continue
↓
Return highest level encountered
Changes :
getData()fetchAsync() methodAnalysis :
Result : MINOR bump (new functionality added)
Input : Current version, proposed version, change list Output : Validation result (valid/invalid) with reasoning
1.5.3 → 2.0.0 ✅ (MINOR and PATCH reset)1.5.3 → 1.6.0 ✅ (PATCH reset)1.5.3 → 1.5.4 ✅ (no reset needed)Valid :
1.2.3 → 2.0.0 with breaking changes ✅1.2.3 → 1.3.0 with new features ✅1.2.3 → 1.2.4 with bug fixes ✅Invalid :
1.2.3 → 1.4.0 (skipped MINOR version) ❌1.2.3 → 2.1.0 (MINOR not reset to 0) ❌1.2.3 → 1.2.3 (no change) ❌1.2.3 → 1.3.0 with breaking changes (under-versioned) ❌1.2.3 → 2.0.0 with only bug fixes (over-versioned) ❌Wrong : ^7.1.5 → ^7.1.6 = "Major" because of the caret Right : ^7.1.5 → ^7.1.6 = PATCH (ignore the ^, compare numbers)
Wrong : Core package changed → must be MAJOR Right : Classify by version numbers, not package importance
Wrong : 1.5.3 → 2.1.0 for MAJOR bump Right : 1.5.3 → 2.0.0 for MAJOR bump (reset MINOR and PATCH)
Wrong : Security fix → must be PATCH Right : Security fixes can be any level (breaking fix = MAJOR)
1.0.0-alpha.1 - Alpha pre-release1.0.0-beta.2 - Beta pre-release1.0.0-rc.1 - Release candidate1.0.0-alpha.1
< 1.0.0-alpha.beta
< 1.0.0-beta
< 1.0.0-beta.2
< 1.0.0-rc.1
< 1.0.0
1.0.0 → 1.0.0-alpha.1 = Pre-release (no semver bump)1.0.0-beta.1 → 1.0.0 = Release (no semver change)1.0.0-rc.1 → 1.1.0 = MINOR release from RCRequired Research :
Time Investment : High (30-60 minutes)
Required Research :
Time Investment : Medium (10-20 minutes)
Required Research :
Time Investment : Low (2-5 minutes)
# View outdated packages with version info
npm outdated
# Machine-readable upgrade information
npx ncu --jsonUpgraded
# pnpm version check
pnpm outdated
# Classify version difference
semver diff 1.2.3 1.3.0 # Output: "minor"
# Compare versions
semver gt 1.3.0 1.2.3 # Output: true
# Check range satisfaction
semver satisfies 1.2.4 "^1.2.3" # Output: true
**Recommended Version Bump**: [MAJOR/MINOR/PATCH]
**Current Version**: X.Y.Z
**Proposed Version**: A.B.C
**Change Summary**:
- [Breaking/Feature/Fix]: Description
**Reasoning**:
[Explain why this classification based on change types]
**Migration Notes** (if MAJOR):
[Required steps for consumers]
**Package**: package-name
**Version Change**: X.Y.Z → A.B.C
**Classification**: [MAJOR/MINOR/PATCH]
**Impact Assessment**:
- Breaking Changes: [Yes/No]
- New Features: [Yes/No]
- Security Fixes: [Yes/No]
**Recommended Action**: [Update now/Test first/Review carefully]
| Old Version | New Version | Change Type | Classification |
|---|---|---|---|
| 1.2.3 | 2.0.0 | X changed | MAJOR |
| 1.2.3 | 1.3.0 | Y changed | MINOR |
| 1.2.3 | 1.2.4 | Z changed | PATCH |
| ^4.0.0 | ^5.0.0 | X changed | MAJOR |
| ~1.2.3 | ~1.3.0 | Y changed | MINOR |
| 9.35.0 | 9.36.0 | Y changed | MINOR |
| 0.2.3 | 0.3.0 | Y changed | MINOR (0.x) |
For complete semver rules and standards, see: ~/.claude/standards/semver.md
Weekly Installs
0
Repository
First Seen
Jan 1, 1970
Security Audits
agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试
136,300 周安装