[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVWCETBQ2MMMSVE0RMS8Y9":3,"skill-same:01M7EVWCETBQ2MMMSVE0RMS8Y9":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVWCETBQ2MMMSVE0RMS8Y9","ams-semantic-versioning-pro",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-semantic-versioning-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: semantic-versioning-pro\ndescription: Apply semantic versioning correctly: MAJOR.MINOR.PATCH discipline, breaking-change detection, and version policies. Use when versioning libraries, APIs, or packages.\ncategory: development\n---\n\n# Semantic Versioning Pro\n\n## Overview\n\nSemantic versioning — **MAJOR.MINOR.PATCH** — is a *contract with your consumers*: given a version\nnumber, they know what kind of change to expect. MAJOR = breaking, MINOR = backward-compatible\nfeatures, PATCH = backward-compatible fixes. The discipline isn't in the numbers — it's in honestly\nclassifying changes and respecting what each bump promises.\n\nThe through-line: the version number is a promise — break it and you break trust, not just builds.\n\n## When to use\n\n- Versioning a library, SDK, API, or package.\n- Deciding whether a change is major, minor, or patch.\n- Setting up automated versioning (changesets, semantic-release).\n- Defining deprecation and breaking-change policies.\n- Reviewing version bumps in releases.\n\n## Core concepts\n\n- **The contract.** MAJOR: incompatible API changes. MINOR: new functionality, backward compatible.\n  PATCH: bug fixes, backward compatible. Consumers on `^1.2.3` get minors and patches automatically —\n  every bump is a promise about what *won't* break them.\n- **What counts as breaking.** Removing\u002Frenaming public APIs, changing signatures or return shapes,\n  altering behavior consumers depend on, dropping supported platforms\u002Fversions, changing default\n  behavior. When in doubt, it's breaking — consumers depend on more than you think.\n- **Public API surface, defined.** Semver applies to the *declared* public API — document what's\n  public (exported symbols, documented endpoints) vs internal. Undocumented internals changing\n  isn't breaking; but if consumers *use* it, expect anger anyway. Be explicit.\n- **Zero-major special case.** `0.x.y`: anything may change; the API is unstable by declaration.\n  Don't linger in 0.x for widely-used software — it's a signal, and prolonged 0.x erodes the\n  signal's meaning. 1.0.0 declares stability intent.\n- **Pre-releases and build metadata.** `1.0.0-rc.1`, `2.0.0-beta.3` — for soaking breaking changes\n  before the major lands. Pre-releases don't satisfy normal ranges (`^1.0.0` won't take `2.0.0-rc.1`),\n  which is exactly the safety you want.\n- **Deprecation policy.** Never break without warning: deprecate in a minor (with warnings\u002Flogs\n  pointing to the migration), remove in the next major. Give consumers at least one full minor\n  series to migrate — breaking-change timelines are a trust instrument.\n\n## Practical workflow\n\n1. **Define the public API.** Document what's covered by semver (and what isn't). For libraries:\n   exported functions\u002Ftypes; for HTTP APIs: endpoints, fields, status codes, auth behavior.\n2. **Classify every change.** In each PR: breaking? → major; new compatible feature? → minor;\n   fix only? → patch. Make classification part of review — it's a design decision, not bookkeeping.\n3. **Automate the mechanics.** Changesets (human-written, per-PR: patch\u002Fminor\u002Fmajor + description)\n   or semantic-release (from conventional commits). Humans classify; machines bump and publish.\n4. **Deprecate before removing.** Minor release: add the new way, deprecate the old with warnings\n   and migration docs. Next major: remove. Never surprise-break.\n5. **Publish pre-releases for majors.** `-rc.1` weeks before the major; invite consumers to test;\n   fix the fallout *before* the major lands. Majors are the highest-stakes releases — soak them.\n6. **Enforce in CI.** Breaking-change detection (API diff tools: `cargo semver-checks`,\n   `revapi`, `japicmp`, public-API snapshots), and changelog entries matching the bump level.\n\nClassification guide:\n\n```text\nMAJOR (breaking):\n  - Remove\u002Frename public function, class, endpoint, or field\n  - Change parameter types\u002Forder, return shapes\n  - Change default behavior consumers may rely on\n  - Drop support for a runtime\u002Fplatform version\n  - Tighten validation (previously-accepted input now rejected)\n\nMINOR (new, compatible):\n  - Add new function\u002Fendpoint\u002Ffield (optional)\n  - Add new optional parameter\n  - Deprecate (without removing) existing API\n  - Performance improvements with identical behavior\n\nPATCH (fix, compatible):\n  - Fix incorrect behavior to match documented contract\n  - Security fix with no API change\n  - Docs, internal refactoring, dependency updates\n```\n\n## Common pitfalls\n\n- **Breaking in a minor.** \"It's a small change\" — but it removed a field someone parsed.\n  If any reasonable consumer could break, it's major. Err toward major.\n- **0.x forever.** A widely-depended `0.14.2` where every minor breaks consumers — the version\n  number lies about stability. Ship 1.0 when the API is used in production by others.\n- **Patch bumps with behavior change.** \"Fixing\" behavior consumers depended on (even if the old\n  behavior was buggy) — that's a breaking change wearing a patch costume. Hyrum's law: all\n  observable behaviors will be depended on.\n- **No deprecation path.** Removing APIs in the same release they're deprecated — or without\n  deprecation at all. The deprecation period *is* the migration budget you give consumers.\n- **Version ranges misunderstood.** Publishing a breaking change as minor breaks every consumer\n  on `^` ranges simultaneously — a distributed outage of trust. This is why classification matters.\n- **Forgetting the ecosystem.** Bumping major without checking downstream (plugins, adapters,\n  docs, examples) — the release isn't done until the ecosystem story is coherent.\n- **Manual versioning drift.** Humans forgetting to bump, or bumping inconsistently. Automate\n  (changesets\u002Fsemantic-release); let humans do the classification they uniquely can.\n","# Semantic Versioning Pro\n\n## Overview\n\nSemantic versioning — **MAJOR.MINOR.PATCH** — is a *contract with your consumers*: given a version\nnumber, they know what kind of change to expect. MAJOR = breaking, MINOR = backward-compatible\nfeatures, PATCH = backward-compatible fixes. The discipline isn't in the numbers — it's in honestly\nclassifying changes and respecting what each bump promises.\n\nThe through-line: the version number is a promise — break it and you break trust, not just builds.\n\n## When to use\n\n- Versioning a library, SDK, API, or package.\n- Deciding whether a change is major, minor, or patch.\n- Setting up automated versioning (changesets, semantic-release).\n- Defining deprecation and breaking-change policies.\n- Reviewing version bumps in releases.\n\n## Core concepts\n\n- **The contract.** MAJOR: incompatible API changes. MINOR: new functionality, backward compatible.\n  PATCH: bug fixes, backward compatible. Consumers on `^1.2.3` get minors and patches automatically —\n  every bump is a promise about what *won't* break them.\n- **What counts as breaking.** Removing\u002Frenaming public APIs, changing signatures or return shapes,\n  altering behavior consumers depend on, dropping supported platforms\u002Fversions, changing default\n  behavior. When in doubt, it's breaking — consumers depend on more than you think.\n- **Public API surface, defined.** Semver applies to the *declared* public API — document what's\n  public (exported symbols, documented endpoints) vs internal. Undocumented internals changing\n  isn't breaking; but if consumers *use* it, expect anger anyway. Be explicit.\n- **Zero-major special case.** `0.x.y`: anything may change; the API is unstable by declaration.\n  Don't linger in 0.x for widely-used software — it's a signal, and prolonged 0.x erodes the\n  signal's meaning. 1.0.0 declares stability intent.\n- **Pre-releases and build metadata.** `1.0.0-rc.1`, `2.0.0-beta.3` — for soaking breaking changes\n  before the major lands. Pre-releases don't satisfy normal ranges (`^1.0.0` won't take `2.0.0-rc.1`),\n  which is exactly the safety you want.\n- **Deprecation policy.** Never break without warning: deprecate in a minor (with warnings\u002Flogs\n  pointing to the migration), remove in the next major. Give consumers at least one full minor\n  series to migrate — breaking-change timelines are a trust instrument.\n\n## Practical workflow\n\n1. **Define the public API.** Document what's covered by semver (and what isn't). For libraries:\n   exported functions\u002Ftypes; for HTTP APIs: endpoints, fields, status codes, auth behavior.\n2. **Classify every change.** In each PR: breaking? → major; new compatible feature? → minor;\n   fix only? → patch. Make classification part of review — it's a design decision, not bookkeeping.\n3. **Automate the mechanics.** Changesets (human-written, per-PR: patch\u002Fminor\u002Fmajor + description)\n   or semantic-release (from conventional commits). Humans classify; machines bump and publish.\n4. **Deprecate before removing.** Minor release: add the new way, deprecate the old with warnings\n   and migration docs. Next major: remove. Never surprise-break.\n5. **Publish pre-releases for majors.** `-rc.1` weeks before the major; invite consumers to test;\n   fix the fallout *before* the major lands. Majors are the highest-stakes releases — soak them.\n6. **Enforce in CI.** Breaking-change detection (API diff tools: `cargo semver-checks`,\n   `revapi`, `japicmp`, public-API snapshots), and changelog entries matching the bump level.\n\nClassification guide:\n\n```text\nMAJOR (breaking):\n  - Remove\u002Frename public function, class, endpoint, or field\n  - Change parameter types\u002Forder, return shapes\n  - Change default behavior consumers may rely on\n  - Drop support for a runtime\u002Fplatform version\n  - Tighten validation (previously-accepted input now rejected)\n\nMINOR (new, compatible):\n  - Add new function\u002Fendpoint\u002Ffield (optional)\n  - Add new optional parameter\n  - Deprecate (without removing) existing API\n  - Performance improvements with identical behavior\n\nPATCH (fix, compatible):\n  - Fix incorrect behavior to match documented contract\n  - Security fix with no API change\n  - Docs, internal refactoring, dependency updates\n```\n\n## Common pitfalls\n\n- **Breaking in a minor.** \"It's a small change\" — but it removed a field someone parsed.\n  If any reasonable consumer could break, it's major. Err toward major.\n- **0.x forever.** A widely-depended `0.14.2` where every minor breaks consumers — the version\n  number lies about stability. Ship 1.0 when the API is used in production by others.\n- **Patch bumps with behavior change.** \"Fixing\" behavior consumers depended on (even if the old\n  behavior was buggy) — that's a breaking change wearing a patch costume. Hyrum's law: all\n  observable behaviors will be depended on.\n- **No deprecation path.** Removing APIs in the same release they're deprecated — or without\n  deprecation at all. The deprecation period *is* the migration budget you give consumers.\n- **Version ranges misunderstood.** Publishing a breaking change as minor breaks every consumer\n  on `^` ranges simultaneously — a distributed outage of trust. This is why classification matters.\n- **Forgetting the ecosystem.** Bumping major without checking downstream (plugins, adapters,\n  docs, examples) — the release isn't done until the ecosystem story is coherent.\n- **Manual versioning drift.** Humans forgetting to bump, or bumping inconsistently. Automate\n  (changesets\u002Fsemantic-release); let humans do the classification they uniquely can.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-semantic-versioning-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-semantic-versioning-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-semantic-versioning-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-semantic-versioning-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-semantic-versioning-pro\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]