تخطَّ إلى المحتوى
TakoAPI
العودة إلى المهارات

semver-helper

بواسطة avegancafe

Coding Agents & IDEs
372التنزيلات وفق ما يذكره clawskills.sh
0المشاهدات
لا إعجاباتسجّل الدخول للإعجاب بهذه المهارة
—لم يُقيَّم بعد
تقييمك

موجز

Semantic Versioning 2.0.0 reference guide.

الوصف

ما الذي تفعله هذه المهارة

Reference guide for Semantic Versioning 2.0.0 decisions. Covers when to increment MAJOR, MINOR, or PATCH, with a decision tree, real examples, pre-release naming, and common edge cases.

Cuts through the full semver spec with a decision tree and concrete examples, so you get an answer in seconds instead of reading documentation.

متى تستخدمها

  • Deciding whether removing a deprecated API endpoint requires a MAJOR bump
  • Checking which number to increment before publishing an npm package
  • Resolving the correct bump when a PR contains both a bug fix and a new feature
  • Picking the right pre-release label (alpha, beta, rc) before a stable release
  • Confirming whether an internal refactor that preserves behavior needs a version change

مثال على سير العمل

الإدخال

User asks: I renamed a public function from removeUser() to deleteUser() — what version should I bump to?

الوكيل
  1. 1

    Check whether the change affects something users depend on

  2. 2

    Identify the rename as a breaking change, since users must update all call sites

  3. 3

    Apply the MAJOR bump rule: breaking changes increment the first number

  4. 4

    Note that MINOR and PATCH reset to 0 after a MAJOR bump

الإخراج

Bump to the next MAJOR version (e.g. 1.2.3 → 2.0.0), since renaming a public function is a breaking API change.

التثبيت

clawhub install avegancafe/semver-helper

شغّل أمر واجهة سطر الأوامر، أو الصق النص في Claude Code أو Cursor أو Codex أو أي وكيل برمجة تستخدمه.

الروابط