[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B3568G9BW8MNZPXDFDBF6F":3,"skill-same:01M7B3568G9BW8MNZPXDFDBF6F":58},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7B3568G9BW8MNZPXDFDBF6F","release-notes",null,"Generate user-facing release notes for Hamster Studio. Analyzes commits and code changes between versions to produce clear, technical release notes.","gethamster\u002Fskills","gethamster","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F215697643?v=4","01M7B2R6PGB3SDZZ71E0WE2S74","Hamster","01M7B2R6Q21HWJRXZZWB78BNDG",4,"MIT","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Frelease-notes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release-notes\ndescription: \"Generate user-facing release notes for Hamster Studio. Analyzes commits and code changes between versions to produce clear, technical release notes.\"\nversion: \"1.1.0\"\n---\n\n# Release Notes Generation\n\n## Overview\n\nGenerate release notes that tell users exactly what changed and why they should care. Analyze the actual code changes, not just commit messages, to understand what shipped.\n\n## When to Use\n\nThis skill is triggered by the CI workflow after a new version is tagged. It receives:\n\n- The new version tag (e.g., `v0.29.0`)\n- The previous version tag for comparison\n\n## Process\n\n### 1. Gather Context\n\n```bash\n# Get commits between versions\ngit log --format=\"- %s (%h)\" $PREVIOUS_TAG..$NEW_TAG\n\n# Get changed files\ngit diff --stat $PREVIOUS_TAG..$NEW_TAG\n\n# Get detailed changes for key areas\ngit diff $PREVIOUS_TAG..$NEW_TAG -- apps\u002Fweb\u002Fapp apps\u002Fai\u002Fsrc packages\u002F\n```\n\n### 2. Analyze Changes\n\nFor each significant change:\n\n1. Read the modified files to understand what actually changed\n2. Identify user-facing impact (new feature, bug fix, behavior change)\n3. Group related changes together\n\nFocus areas:\n\n- `apps\u002Fweb\u002Fapp\u002F` - New pages, UI changes, user flows\n- `apps\u002Fai\u002Fsrc\u002F` - API changes, new endpoints, AI features\n- `packages\u002F` - Shared functionality changes\n- `apps\u002Fweb\u002Fsupabase\u002Fschemas\u002F` - Data model changes\n\n### 3. Write Release Notes\n\nFollow the format in `references\u002Fwriting-guidelines.md`. Key principles:\n\n- **Summary**: 2-3 sentences stating what shipped. No hype.\n- **Sections**: Group into 3-5 categories with clear headings\n- **Technical audience**: They want specifics, not marketing language\n- **User impact**: Explain what users can now do, not implementation details\n\n### 4. Output\n\nOutput the release notes as markdown that will be set as the GitHub Release body.\n\n## Output Format\n\n```markdown\n# Release X.Y.Z\n\n## Summary\n\n[2-3 sentences stating exactly what shipped]\n\n## [Category 1]\n\n[Description of changes]\n\n## [Category 2]\n\n[Description of changes]\n\n## Bug Fixes\n\n- [Fix 1]\n- [Fix 2]\n```\n\n## Quality Checklist\n\nBefore finalizing:\n\n- [ ] Summary captures the release's main value\n- [ ] No marketing fluff or banned phrases\n- [ ] Technical details are accurate (verified against code)\n- [ ] User impact is clear for each change\n- [ ] Internal refactors excluded unless they affect UX\n- [ ] No PR links or commit hashes in output\n\n## References\n\n- `references\u002Fwriting-guidelines.md` - Format rules and banned phrases\n- `references\u002Fexamples.md` - Example release notes from previous versions\n","# Release Notes Generation\n\n## Overview\n\nGenerate release notes that tell users exactly what changed and why they should care. Analyze the actual code changes, not just commit messages, to understand what shipped.\n\n## When to Use\n\nThis skill is triggered by the CI workflow after a new version is tagged. It receives:\n\n- The new version tag (e.g., `v0.29.0`)\n- The previous version tag for comparison\n\n## Process\n\n### 1. Gather Context\n\n```bash\n# Get commits between versions\ngit log --format=\"- %s (%h)\" $PREVIOUS_TAG..$NEW_TAG\n\n# Get changed files\ngit diff --stat $PREVIOUS_TAG..$NEW_TAG\n\n# Get detailed changes for key areas\ngit diff $PREVIOUS_TAG..$NEW_TAG -- apps\u002Fweb\u002Fapp apps\u002Fai\u002Fsrc packages\u002F\n```\n\n### 2. Analyze Changes\n\nFor each significant change:\n\n1. Read the modified files to understand what actually changed\n2. Identify user-facing impact (new feature, bug fix, behavior change)\n3. Group related changes together\n\nFocus areas:\n\n- `apps\u002Fweb\u002Fapp\u002F` - New pages, UI changes, user flows\n- `apps\u002Fai\u002Fsrc\u002F` - API changes, new endpoints, AI features\n- `packages\u002F` - Shared functionality changes\n- `apps\u002Fweb\u002Fsupabase\u002Fschemas\u002F` - Data model changes\n\n### 3. Write Release Notes\n\nFollow the format in `references\u002Fwriting-guidelines.md`. Key principles:\n\n- **Summary**: 2-3 sentences stating what shipped. No hype.\n- **Sections**: Group into 3-5 categories with clear headings\n- **Technical audience**: They want specifics, not marketing language\n- **User impact**: Explain what users can now do, not implementation details\n\n### 4. Output\n\nOutput the release notes as markdown that will be set as the GitHub Release body.\n\n## Output Format\n\n```markdown\n# Release X.Y.Z\n\n## Summary\n\n[2-3 sentences stating exactly what shipped]\n\n## [Category 1]\n\n[Description of changes]\n\n## [Category 2]\n\n[Description of changes]\n\n## Bug Fixes\n\n- [Fix 1]\n- [Fix 2]\n```\n\n## Quality Checklist\n\nBefore finalizing:\n\n- [ ] Summary captures the release's main value\n- [ ] No marketing fluff or banned phrases\n- [ ] Technical details are accurate (verified against code)\n- [ ] User impact is clear for each change\n- [ ] Internal refactors excluded unless they affect UX\n- [ ] No PR links or commit hashes in output\n\n## References\n\n- `references\u002Fwriting-guidelines.md` - Format rules and banned phrases\n- `references\u002Fexamples.md` - Example release notes from previous versions\n",{"name":5,"version":24,"description":7},"1.1.0","main","fe3bb1476c3ec23d8a366eac0fa8cd9f0852360a","skills\u002F.experimental\u002Frelease-notes",0,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgethamster","https:\u002F\u002Ftryhamster.com","We're building the AI-native future of work, unlocking the promised acceleration for your whole team, from idea to impact.","2026-11-05 11:33:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add gethamster\u002Fskills --skill release-notes",{"tool":40,"command":41},"bunx","bunx skills add gethamster\u002Fskills --skill release-notes",{"tool":43,"command":44},"pnpm","pnpm dlx skills add gethamster\u002Fskills --skill release-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Frelease-notes\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fexamples.md","REFERENCE","参考文档",6001,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Frelease-notes\u002Freferences\u002Fexamples.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fwriting-guidelines.md",2737,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Frelease-notes\u002Freferences\u002Fwriting-guidelines.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7B5MWYW0KE251276S56KQDZ","writing-waterfall-requirements-documents","Write a waterfall requirements document: elicit, structure and review testable, traceable requirements, then baseline the specification before design.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-waterfall-requirements-documents\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7B5MRCXWWPKREPB1CHQ7H90","writing-vision-and-values-statements","Write a V2MOM vision a reader can test and a ranked list of values that settles real tradeoffs, so the rest of the document has a clear anchor.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-vision-and-values-statements\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7B5MKH2CH22YZAHQW3080VQ","writing-system-prompts-for-claude","Write Claude prompts and CLAUDE.md files that supply exact inputs, scope the task, and define done so the first attempt can be checked.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-system-prompts-for-claude\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7B5ME1Y3X9RNRKP5HKHKACZ","writing-page-specific-website-copy","Website copywriting by page type: write homepage, landing page, pricing page and feature page copy that fits each page's visitor and single job.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-page-specific-website-copy\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7B5M8MQNM8MN8PYH6BVWJ2B","writing-internal-press-releases","How to write an internal press release: the one-page working backwards press release that opens a PR\u002FFAQ document before anything is built.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-internal-press-releases\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7B5M3P3YH1XF37R8PWXXSBK","writing-email-sequences-that-sell","Email sequence copywriting for nurture and sales: give each email one job, write clear subject lines, and close with one specific call to action.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-email-sequences-that-sell\u002FSKILL.md",[],[]]