[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M748F37AW4DFBRRK043RPBAX":3,"skill-same:01M748F37AW4DFBRRK043RPBAX":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M748F37AW4DFBRRK043RPBAX","git-release",null,"Semantic versioning and release workflow for creating and publishing package releases.","itlackey\u002Fakm-eval","itlackey","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6414031?v=4","01M6D08NHES2CPRGY5HCPJECD6","IT Lackey","01M71W0ZJQ3686SNJSCQZM3X4E",0,"MPL-2.0","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fdistill\u002Fassets\u002Fbundles\u002Fasset-03\u002Fskills\u002Fcoding\u002Fgit-release\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: git-release\ndescription: Semantic versioning and release workflow for creating and\n  publishing package releases.\nwhen_to_use: Use this skill when preparing a new software release and you need a\n  consistent semantic versioning and changelog workflow.\nupdated: 2026-05-17\n---\n\n# Git Release\n\nThis skill documents a small, repeatable release workflow using semantic versioning (SemVer) and a changelog. It focuses on the schema and structure of the release process so teams can follow a consistent pattern.\n\n## When To Use\nUse this when you are about to publish a new release (library, CLI, service) and need to:\n- Choose the next SemVer number.\n- Update the changelog with a short summary of notable changes under the new version heading.\n- Update the project's version metadata (`package.json`, `pyproject.toml`, `go.mod`, etc.) if applicable.\n- Tag the release in git and push artifacts\u002Ftags.\n\n## Versioning (SemVer)\n- **MAJOR**: Incompatible API changes or breaking changes.\n- **MINOR**: Backwards-compatible new features or enhancements.\n- **PATCH**: Backwards-compatible bug fixes and small tweaks.\n\nTag format recommendation: `vMAJOR.MINOR.PATCH` (for example `v1.2.3`).\n\n## Release Process (Structured Steps)\n1. Determine the next version (MAJOR.MINOR.PATCH) based on merged changes and SemVer rules.\n2. Update the changelog with a short summary of notable changes under the new version heading.\n3. Update the project's version metadata (`package.json`, `pyproject.toml`, `go.mod`, etc.) if applicable.\n4. Commit the version and changelog changes to the release branch.\n5. Create a signed or annotated git tag using the chosen tag format.\n6. Push commits and tags to the remote repository.\n7. Publish artifacts (package registry, container registry, GitHub Release) according to your release pipeline.\n\n## Minimal Command Examples\n- Commit and tag (example):\n  - `git add CHANGELOG.md package.json && git commit -m \"chore(release): v1.2.0\"`\n  - `git tag -a v1.2.0 -m \"Release v1.2.0\"`\n  - `git push origin main --follow-tags`\n\n- Using npm for version bump (example):\n  - `npm version patch -m \"chore(release): %s\"` (creates commit + tag)\n  - `git push origin --follow-tags`\n\nAdjust these commands to match your language\u002Ftooling conventions.\n\n## Changelog Guidance\n- Put a short, human-readable entry for each noteworthy change under the new version heading.\n- Use categories if helpful (e.g., Added, Changed, Fixed, Security).\n- Prefer linkable references to PR numbers or issue IDs for traceability.\n\n## Notes & Conventions\n- Keep tag names consistent (recommended: leading `v`).\n- Prefer annotated tags when you want release messages and signing: `git tag -a vX.Y.Z -m \"Release vX.Y.Z\"`.\n- Ensure CI\u002FCD or release automation uses the same version source (tag or file) to avoid drift.\n\n## Minimal Checklist\n- [ ] Version chosen and validated\n- [ ] CHANGELOG updated\n- [ ] Version metadata updated (if needed)\n- [ ] Commit created with release changes\n- [ ] Tag created (annotated or signed)\n- [ ] Commits and tags pushed\n- [ ] Artifacts published\n","# Git Release\n\nThis skill documents a small, repeatable release workflow using semantic versioning (SemVer) and a changelog. It focuses on the schema and structure of the release process so teams can follow a consistent pattern.\n\n## When To Use\nUse this when you are about to publish a new release (library, CLI, service) and need to:\n- Choose the next SemVer number.\n- Update the changelog with a short summary of notable changes under the new version heading.\n- Update the project's version metadata (`package.json`, `pyproject.toml`, `go.mod`, etc.) if applicable.\n- Tag the release in git and push artifacts\u002Ftags.\n\n## Versioning (SemVer)\n- **MAJOR**: Incompatible API changes or breaking changes.\n- **MINOR**: Backwards-compatible new features or enhancements.\n- **PATCH**: Backwards-compatible bug fixes and small tweaks.\n\nTag format recommendation: `vMAJOR.MINOR.PATCH` (for example `v1.2.3`).\n\n## Release Process (Structured Steps)\n1. Determine the next version (MAJOR.MINOR.PATCH) based on merged changes and SemVer rules.\n2. Update the changelog with a short summary of notable changes under the new version heading.\n3. Update the project's version metadata (`package.json`, `pyproject.toml`, `go.mod`, etc.) if applicable.\n4. Commit the version and changelog changes to the release branch.\n5. Create a signed or annotated git tag using the chosen tag format.\n6. Push commits and tags to the remote repository.\n7. Publish artifacts (package registry, container registry, GitHub Release) according to your release pipeline.\n\n## Minimal Command Examples\n- Commit and tag (example):\n  - `git add CHANGELOG.md package.json && git commit -m \"chore(release): v1.2.0\"`\n  - `git tag -a v1.2.0 -m \"Release v1.2.0\"`\n  - `git push origin main --follow-tags`\n\n- Using npm for version bump (example):\n  - `npm version patch -m \"chore(release): %s\"` (creates commit + tag)\n  - `git push origin --follow-tags`\n\nAdjust these commands to match your language\u002Ftooling conventions.\n\n## Changelog Guidance\n- Put a short, human-readable entry for each noteworthy change under the new version heading.\n- Use categories if helpful (e.g., Added, Changed, Fixed, Security).\n- Prefer linkable references to PR numbers or issue IDs for traceability.\n\n## Notes & Conventions\n- Keep tag names consistent (recommended: leading `v`).\n- Prefer annotated tags when you want release messages and signing: `git tag -a vX.Y.Z -m \"Release vX.Y.Z\"`.\n- Ensure CI\u002FCD or release automation uses the same version source (tag or file) to avoid drift.\n\n## Minimal Checklist\n- [ ] Version chosen and validated\n- [ ] CHANGELOG updated\n- [ ] Version metadata updated (if needed)\n- [ ] Commit created with release changes\n- [ ] Tag created (annotated or signed)\n- [ ] Commits and tags pushed\n- [ ] Artifacts published\n",{"name":5,"updated":24,"description":7,"when_to_use":25},1778976000000,"Use this skill when preparing a new software release and you need a consistent semantic versioning and changelog workflow.","main","b293a8475fcbb20683373dc9735a2ecf0ca7889d","evals\u002Fdistill\u002Fassets\u002Fbundles\u002Fasset-03\u002Fskills\u002Fcoding\u002Fgit-release","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval","https:\u002F\u002Fgithub.com\u002Fitlackey","2026-11-13 11:49:12",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add itlackey\u002Fakm-eval --skill git-release",{"tool":38,"command":39},"bunx","bunx skills add itlackey\u002Fakm-eval --skill git-release",{"tool":41,"command":42},"pnpm","pnpm dlx skills add itlackey\u002Fakm-eval --skill git-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fdistill\u002Fassets\u002Fbundles\u002Fasset-03\u002Fskills\u002Fcoding\u002Fgit-release\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M748G6310YQEN9SEY8E69V7F","tax-filing-checklist","Walk through the steps and documents needed to file an individual federal income tax return","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Ftax-filing-checklist\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M748G3C1CSMBM33KP2CCK7TB","patient-vitals-charting","Record patient vital signs consistently and flag values outside the normal reference range","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fpatient-vitals-charting\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M748G05H68QFB8YVQKDHF66B","pasta-from-scratch","Make fresh egg pasta dough from scratch, roll it, and cut it into shapes","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fpasta-from-scratch\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M748FXAQVJRX98HP8STRTD9P","knife-sharpening","Sharpen and hone kitchen knives to keep an edge safe and effective","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fknife-sharpening\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M748FTJEZ0P6BXNERTHZ9KB3","first-aid-response","Respond to a first aid emergency using a scene-safety-first, ABC-based (airway, breathing, circulation) approach","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Ffirst-aid-response\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M748FQESZPA3ZW5SWKJNKMD0","contract-review-basics","Review a contract draft for missing terms, ambiguous language, and risky clauses before signing","https:\u002F\u002Fgithub.com\u002Fitlackey\u002Fakm-eval\u002Fblob\u002Fmain\u002Fevals\u002Fretrieval\u002Fassets\u002Fbooks\u002Flibrary\u002Fskills\u002Fcontract-review-basics\u002FSKILL.md",[],[]]