[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JMJJZWNENYNF50GNC6TSZ":3,"skill-same:01M75JMJJZWNENYNF50GNC6TSZ":60},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75JMJJZWNENYNF50GNC6TSZ","writing-release-notes",null,"Generates release notes from merged pull requests, grouping the changes into features, fixes, and chores so the notes read clearly. Use when the user asks to draft release notes, write a changelog, summarize merged PRs into release notes, or any time you need to write something describing recent code changes.","mjenkinsx9\u002Fskill-testing","mjenkinsx9","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F238907794?v=4","01M75JK4ZXAC73W2JPJM81TYE9","Mike Jenkins","01M75JK50GA8MEGAHXDST0E3C4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Fstaging\u002Fwriting-release-notes\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: writing-release-notes\ndescription: Generates release notes from merged pull requests, grouping the changes into features, fixes, and chores so the notes read clearly. Use when the user asks to draft release notes, write a changelog, summarize merged PRs into release notes, or any time you need to write something describing recent code changes.\n---\n\n\u003C!-- DEMO FIXTURE for the learnings-seeding path (improving-skills tests.md).\n     This SKILL.md carries intentional slop — an over-broad description\n     catch-all, a duplicated step, a duplicated section, and a filler intro —\n     all flagged as `Status: open` candidate edits in references\u002Flearnings.md.\n     \u002Fimproving-skills should seed those entries and apply them. Do not \"fix\"\n     this by hand; it is the input state for a reproducible test. -->\n\n# Writing Release Notes\n\nThis skill helps you write release notes. Release notes are a document that\ndescribes what changed in a release. Writing good release notes is important\nbecause users want to know what changed in the new version of the software.\n\n## When to use\n\nWhen the user asks for release notes or a changelog assembled from a set of\nmerged pull requests.\n\n## Steps\n\n1. Collect the merged pull requests for the release.\n2. Group each pull request into one of three categories: features, fixes, chores.\n3. Write a one-line summary for each pull request.\n4. Group the summaries by category (features, fixes, chores).\n5. Assemble the grouped summaries into the final document.\n\n## Output format\n\nEmit markdown with an H2 heading per category and a bullet per change:\n\n```\n## Features\n- \u003Cchange>\n## Fixes\n- \u003Cchange>\n## Chores\n- \u003Cchange>\n```\n\n## Formatting the notes\n\nFormat the output as markdown. Use an H2 heading for each category (Features,\nFixes, Chores) and a bullet list of the changes under each heading.\n\n## Learnings\n\nRetro observations from real runs live in\n[references\u002Flearnings.md](references\u002Flearnings.md).\n","\u003C!-- DEMO FIXTURE for the learnings-seeding path (improving-skills tests.md).\n     This SKILL.md carries intentional slop — an over-broad description\n     catch-all, a duplicated step, a duplicated section, and a filler intro —\n     all flagged as `Status: open` candidate edits in references\u002Flearnings.md.\n     \u002Fimproving-skills should seed those entries and apply them. Do not \"fix\"\n     this by hand; it is the input state for a reproducible test. -->\n\n# Writing Release Notes\n\nThis skill helps you write release notes. Release notes are a document that\ndescribes what changed in a release. Writing good release notes is important\nbecause users want to know what changed in the new version of the software.\n\n## When to use\n\nWhen the user asks for release notes or a changelog assembled from a set of\nmerged pull requests.\n\n## Steps\n\n1. Collect the merged pull requests for the release.\n2. Group each pull request into one of three categories: features, fixes, chores.\n3. Write a one-line summary for each pull request.\n4. Group the summaries by category (features, fixes, chores).\n5. Assemble the grouped summaries into the final document.\n\n## Output format\n\nEmit markdown with an H2 heading per category and a bullet per change:\n\n```\n## Features\n- \u003Cchange>\n## Fixes\n- \u003Cchange>\n## Chores\n- \u003Cchange>\n```\n\n## Formatting the notes\n\nFormat the output as markdown. Use an H2 heading for each category (Features,\nFixes, Chores) and a bullet list of the changes under each heading.\n\n## Learnings\n\nRetro observations from real runs live in\n[references\u002Flearnings.md](references\u002Flearnings.md).\n",{"name":5,"description":7},"main","84a1f9a57e593326b40237ffa221cdea06744279","staging\u002Fwriting-release-notes","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9","mikejenkins.us","IT Infrastructure Leader (17+ yrs) | Team Builder & Mentor | Datacenter Manager | Agentic Engineering Explorer | Forever Learning","2026-06-18 20:59:34",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add mjenkinsx9\u002Fskill-testing --skill writing-release-notes",{"tool":38,"command":39},"bunx","bunx skills add mjenkinsx9\u002Fskill-testing --skill writing-release-notes",{"tool":41,"command":42},"pnpm","pnpm dlx skills add mjenkinsx9\u002Fskill-testing --skill writing-release-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Fstaging\u002Fwriting-release-notes\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Flearnings.md","REFERENCE","参考文档",1476,"https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Fstaging\u002Fwriting-release-notes\u002Freferences\u002Flearnings.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"test-prompts.md",658,"https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Fstaging\u002Fwriting-release-notes\u002Ftest-prompts.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"tests.md",590,"https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Fstaging\u002Fwriting-release-notes\u002Ftests.md",[61,68,75,82,89,96],{"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},"01M75JMFQ3NCF3DEAAE69Y7VTJ","generating-ai-ideas","Orchestrates a council of specialized perspectives to generate, stress-test, and refine high-quality, sellable AI-related business and product ideas. Use when the user wants validated AI business opportunities, AI product concepts, or AI tooling ideas with clear go-to-market paths.","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Fstaging\u002Fgenerating-ai-ideas\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},"01M75JMBCNHWSNZWRBKEKC12XC","reviewing-pull-requests","Reviews a pull request diff against a structured rubric covering correctness, tests, security, and style, then produces a prioritized comment list. Use when the user asks to review a PR, audit a diff, or check changes before merging.","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Fexamples\u002Freviewing-pull-requests\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},"01M75JM8H8XDRCME1Q9G75PVGA","winpath-in-reference","Audits widget docs for path portability. Use when the user asks to audit fixture path portability, scan widget references for backslash paths, or vet doc hygiene.","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Feval\u002Ftests\u002Ffixtures\u002Fwinpath-in-reference\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},"01M75JM677QX1QHJNJV1XPB061","vague-trigger","Generates widget summaries for engineers and is helpful for data processing tasks generally.","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Feval\u002Ftests\u002Ffixtures\u002Fvague-trigger\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M75JM49TCWDTBDJDHBJAP8RY","stale-tests","Refreshes widget fixture baselines on demand. Use when the user asks to refresh fixture baselines, re-verify widget scenarios, or rebaseline gizmo outputs.","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Feval\u002Ftests\u002Ffixtures\u002Fstale-tests\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M75JM0SQBQ3DG2F1VBWB64GK","smell-in-script","Installs the widget toolchain via the bundled script. Use when the user asks to install the widget toolchain, bootstrap gizmo tooling, or set up fixture dependencies.","https:\u002F\u002Fgithub.com\u002Fmjenkinsx9\u002Fskill-testing\u002Fblob\u002Fmain\u002Feval\u002Ftests\u002Ffixtures\u002Fsmell-in-script\u002FSKILL.md",[],[]]