chore: llm rules

Author: devridge0

LLM.md

@@ -82,7 +82,7 @@ IntentKit is an autonomous agent framework that enables creation and management
 
 ### Github Release
 1. Make a `git pull` first.
-2. The release number rule is: pre-release is `vX.X.X-devX`, release is `vX.X.X`. When you calculate the next version number, release number should be the last release number patch version + 1, dev number should check both last release and last pre-release, should greater than both. For example, v0.1.2 is greater than v0.1.2-dev1, if v0.1.2 release exist, v0.1.3-dev1 should be the next pre-release version number, then v0.1.3-dev2 is the next pre-release version number before v0.1.3 released.
+2. The release version number rule is follow Semantic Versioning: pre-release is `vA.B.C-devD`, release is `vA.B.C`. When you calculate the next version number, release should +1 to patch version `C`, pre-release should +1 to `D` of `-devD`, but if vA.B.C already released, next pre-release should be restart from next patch version `vA.B.(C+1)-dev1`. For example, next pre-release of v0.1.2-dev3 should be v0.1.2-dev4, but if v0.1.2 production release already published, the next pre-release will restart from v0.1.3-dev1.
 3. Find the last version number in release or pre-release using `git tag --sort=-version:refname | head -15`, diff origin/main with it, summarize the release note to build/changelog.md for later use. Add a diff link to release note too, the from and to should be the version number.
 4. If the release is not pre-release, also insert the release note to the beginning of CHANGELOG.md (This file contains all history release notes, don't use it in gh command), leave this changed CHANGELOG.md in local, don't commit and push it, we will commit it together with next changes.
 5. Construct `gh release create` command, use changelog.md as notes file in gh command.