[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79Y7PTVEECJAFPET5CSB6Q2":3,"skill-same:01M79Y7PTVEECJAFPET5CSB6Q2":54},{"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":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79Y7PTVEECJAFPET5CSB6Q2","write-release-notes",null,"Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. \"write release notes for v1.32.0\", \"generate release notes for the latest release\", \"create changelog for v2.0\").","rizrmd\u002Ffurcode","rizrmd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F126301?v=4","01M79Y66RZGD1KFR6552KV6TZM","Rizky","01M79Y66SH9C61S6JWT9QFZ547",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002F.furcode\u002Fskills\u002Fwrite-release-notes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-release-notes\ndescription: Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. \"write release notes for v1.32.0\", \"generate release notes for the latest release\", \"create changelog for v2.0\").\n---\n\n# Write Release Notes\n\nGenerate clear, informative, and enthusiastic release notes by pulling live data from GitHub and synthesizing every PR into a cohesive narrative.\n\n## Workflow\n\n### 1. Fetch Release Data\n\nRun the bundled script to pull the release metadata and all linked PR details in one shot:\n\n```bash\nbash .forge\u002Fskills\u002Fwrite-release-notes\u002Fscripts\u002Ffetch-release-data.sh \u003Cversion> [owner\u002Frepo]\n```\n\n- `\u003Cversion>`: The release tag (e.g. `v1.32.0`)\n- `[owner\u002Frepo]`: Optional. Defaults to the current repo detected via `gh repo view`.\n\nThe script outputs two sections:\n- `### RELEASE METADATA ###` — tag name, publish date, release name, raw body\n- `### PR DETAILS ###` — one JSON object per PR with: `number`, `title`, `body`, `labels`, `author`, `mergedAt`, `url`\n\n### 2. Categorize Changes\n\nGroup PRs by their conventional commit prefix or label:\n\n| Category | Prefixes \u002F Labels |\n|---|---|\n| Features | `feat`, `type: feature` |\n| Bug Fixes | `fix`, `type: fix` |\n| Performance | `perf` |\n| Refactors | `refactor` |\n| Maintenance | `chore`, `docs`, `ci`, `build`, `deps` |\n\nDependency bumps (e.g. Dependabot PRs) go into Maintenance. Skip PRs with `error: \"not found\"`.\n\n### 3. Write the Release Notes\n\nProduce a Markdown document with the following structure. Keep the tone **informative and enthusiastic** — explain what changed and why it matters, without resorting to marketing fluff.\n\n```markdown\n# [Product Name] [Version] — [Descriptive Tagline]\n\n> One-sentence summary of what this release focuses on.\n\n## What's New\n\n[2-4 sentence narrative covering the biggest features and fixes. \nDescribe what changed and what users can now do. Use active voice. Be factual but upbeat.]\n\n## Highlights\n\n### [Feature\u002FFix Category]\n**[PR Title rephrased as a clear description of the change]**\n[1-2 sentences expanding on the PR description. Explain what changed and what users can now do differently. \nIf the PR body has useful context, distill it. If empty, infer from the title.]\n\n[Repeat for each significant PR — skip pure chores\u002Fdep bumps unless noteworthy]\n\n## Bug Fixes & Reliability\n\n[Bullet list of fixes, each with a brief impact statement]\n\n## Under the Hood\n\n[Brief paragraph or bullet list covering refactors, maintenance, and dep updates — \nkeep it light, acknowledge the work without boring the reader]\n\n## Contributors\n\nA huge thank you to everyone who made this release happen: [list @handles — exclude bots like @dependabot]\n\n---\n**Full changelog**: [GitHub Release link]\n```\n\n### 4. Tone & Style Guidelines\n\n- **Lead with what changed**: \"You can now...\" or \"Forge now...\" beats \"We added...\"\n- **Be specific**: Name the feature and describe what it does, not just the category\n- **Be informative, not marketty**: Avoid vague adjectives like \"seamless\", \"smarter\", \"blazing\", \"powerful\", \"rock-solid\". Instead, state the concrete fact (e.g. \"editor no longer spawns a git process on every keystroke\" beats \"blazing-fast editor\")\n- **Enthusiasm through substance**: Let the actual improvement speak for itself. Use active, direct language.\n- **Short paragraphs**: Max 3 sentences per block\n- **Skip internal jargon**: Translate crate names and internal concepts into plain language\n- **Celebrate contributors**: Name them by handle\n- **Tagline formula**: `[Version] — [Factual Theme Description]` (e.g. \"v1.32.0 — Terminal Context, File Drop Support, Windows Performance\")\n- **No implementation details**: Do not mention internal module names, struct names, function names, crate names, or how something was implemented. Focus purely on what the user experiences or gains.\n- **No PR\u002Fissue references**: Do not include PR numbers, issue numbers, or links to GitHub PRs\u002Fissues in the release notes. Focus on the changes themselves, not their tracking identifiers.\n\n### 5. Contributors Filter\n\nOnly include **external contributors** in the Contributors section — exclude the core team:\n- `@tusharmath`\n- `@amitksingh1490`\n- `@laststylebender14`\n- Bots (e.g. `@dependabot`)\n\nIf no external contributors exist, omit the Contributors section entirely.\n\n### 6. Validate Length\n\nAfter writing the release notes, run the bundled validation script to confirm the output is under 2000 characters:\n\n```bash\necho \"\u003Crelease notes>\" | bash .forge\u002Fskills\u002Fwrite-release-notes\u002Fscripts\u002Fvalidate-release-notes.sh\n```\n\nIf it prints `FAIL`, trim the draft and re-run until it prints `PASS`:\n- Remove the Under the Hood section first\n- Consolidate Bug Fixes into a shorter bullet list\n- Shorten individual PR descriptions to one tight sentence\n- Remove the least impactful Highlights entries\n\n### 7. Output\n\nPrint the final release notes directly in the chat. Do not write to a file unless the user explicitly asks.\n\n## Notes\n\n- The script handles ANSI color codes injected by `gh` CLI automatically.\n- PRs not found (closed without merge, private, etc.) are silently skipped.\n- If the release has no linked PRs in its body, fall back to listing commits between tags:\n  ```bash\n  gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcompare\u002F\u003Cprev_tag>...\u003Cversion> --jq '.commits[].commit.message'\n  ```\n","# Write Release Notes\n\nGenerate clear, informative, and enthusiastic release notes by pulling live data from GitHub and synthesizing every PR into a cohesive narrative.\n\n## Workflow\n\n### 1. Fetch Release Data\n\nRun the bundled script to pull the release metadata and all linked PR details in one shot:\n\n```bash\nbash .forge\u002Fskills\u002Fwrite-release-notes\u002Fscripts\u002Ffetch-release-data.sh \u003Cversion> [owner\u002Frepo]\n```\n\n- `\u003Cversion>`: The release tag (e.g. `v1.32.0`)\n- `[owner\u002Frepo]`: Optional. Defaults to the current repo detected via `gh repo view`.\n\nThe script outputs two sections:\n- `### RELEASE METADATA ###` — tag name, publish date, release name, raw body\n- `### PR DETAILS ###` — one JSON object per PR with: `number`, `title`, `body`, `labels`, `author`, `mergedAt`, `url`\n\n### 2. Categorize Changes\n\nGroup PRs by their conventional commit prefix or label:\n\n| Category | Prefixes \u002F Labels |\n|---|---|\n| Features | `feat`, `type: feature` |\n| Bug Fixes | `fix`, `type: fix` |\n| Performance | `perf` |\n| Refactors | `refactor` |\n| Maintenance | `chore`, `docs`, `ci`, `build`, `deps` |\n\nDependency bumps (e.g. Dependabot PRs) go into Maintenance. Skip PRs with `error: \"not found\"`.\n\n### 3. Write the Release Notes\n\nProduce a Markdown document with the following structure. Keep the tone **informative and enthusiastic** — explain what changed and why it matters, without resorting to marketing fluff.\n\n```markdown\n# [Product Name] [Version] — [Descriptive Tagline]\n\n> One-sentence summary of what this release focuses on.\n\n## What's New\n\n[2-4 sentence narrative covering the biggest features and fixes. \nDescribe what changed and what users can now do. Use active voice. Be factual but upbeat.]\n\n## Highlights\n\n### [Feature\u002FFix Category]\n**[PR Title rephrased as a clear description of the change]**\n[1-2 sentences expanding on the PR description. Explain what changed and what users can now do differently. \nIf the PR body has useful context, distill it. If empty, infer from the title.]\n\n[Repeat for each significant PR — skip pure chores\u002Fdep bumps unless noteworthy]\n\n## Bug Fixes & Reliability\n\n[Bullet list of fixes, each with a brief impact statement]\n\n## Under the Hood\n\n[Brief paragraph or bullet list covering refactors, maintenance, and dep updates — \nkeep it light, acknowledge the work without boring the reader]\n\n## Contributors\n\nA huge thank you to everyone who made this release happen: [list @handles — exclude bots like @dependabot]\n\n---\n**Full changelog**: [GitHub Release link]\n```\n\n### 4. Tone & Style Guidelines\n\n- **Lead with what changed**: \"You can now...\" or \"Forge now...\" beats \"We added...\"\n- **Be specific**: Name the feature and describe what it does, not just the category\n- **Be informative, not marketty**: Avoid vague adjectives like \"seamless\", \"smarter\", \"blazing\", \"powerful\", \"rock-solid\". Instead, state the concrete fact (e.g. \"editor no longer spawns a git process on every keystroke\" beats \"blazing-fast editor\")\n- **Enthusiasm through substance**: Let the actual improvement speak for itself. Use active, direct language.\n- **Short paragraphs**: Max 3 sentences per block\n- **Skip internal jargon**: Translate crate names and internal concepts into plain language\n- **Celebrate contributors**: Name them by handle\n- **Tagline formula**: `[Version] — [Factual Theme Description]` (e.g. \"v1.32.0 — Terminal Context, File Drop Support, Windows Performance\")\n- **No implementation details**: Do not mention internal module names, struct names, function names, crate names, or how something was implemented. Focus purely on what the user experiences or gains.\n- **No PR\u002Fissue references**: Do not include PR numbers, issue numbers, or links to GitHub PRs\u002Fissues in the release notes. Focus on the changes themselves, not their tracking identifiers.\n\n### 5. Contributors Filter\n\nOnly include **external contributors** in the Contributors section — exclude the core team:\n- `@tusharmath`\n- `@amitksingh1490`\n- `@laststylebender14`\n- Bots (e.g. `@dependabot`)\n\nIf no external contributors exist, omit the Contributors section entirely.\n\n### 6. Validate Length\n\nAfter writing the release notes, run the bundled validation script to confirm the output is under 2000 characters:\n\n```bash\necho \"\u003Crelease notes>\" | bash .forge\u002Fskills\u002Fwrite-release-notes\u002Fscripts\u002Fvalidate-release-notes.sh\n```\n\nIf it prints `FAIL`, trim the draft and re-run until it prints `PASS`:\n- Remove the Under the Hood section first\n- Consolidate Bug Fixes into a shorter bullet list\n- Shorten individual PR descriptions to one tight sentence\n- Remove the least impactful Highlights entries\n\n### 7. Output\n\nPrint the final release notes directly in the chat. Do not write to a file unless the user explicitly asks.\n\n## Notes\n\n- The script handles ANSI color codes injected by `gh` CLI automatically.\n- PRs not found (closed without merge, private, etc.) are silently skipped.\n- If the release has no linked PRs in its body, fall back to listing commits between tags:\n  ```bash\n  gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcompare\u002F\u003Cprev_tag>...\u003Cversion> --jq '.commits[].commit.message'\n  ```\n",{"name":5,"description":7},"main","0991cb6197efb0e637e9f4bb5469a6439b001750",".furcode\u002Fskills\u002Fwrite-release-notes","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode","https:\u002F\u002Fgithub.com\u002Frizrmd","2026-10-31 07:19:45",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add rizrmd\u002Ffurcode --skill write-release-notes",{"tool":36,"command":37},"bunx","bunx skills add rizrmd\u002Ffurcode --skill write-release-notes",{"tool":39,"command":40},"pnpm","pnpm dlx skills add rizrmd\u002Ffurcode --skill write-release-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002F.furcode\u002Fskills\u002Fwrite-release-notes\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"scripts\u002Ffetch-release-data.sh","SCRIPT","脚本",1621,"https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002F.furcode\u002Fskills\u002Fwrite-release-notes\u002Fscripts\u002Ffetch-release-data.sh",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fvalidate-release-notes.sh",708,"https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002F.furcode\u002Fskills\u002Fwrite-release-notes\u002Fscripts\u002Fvalidate-release-notes.sh",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79Y84CFK1DBH5CF6V236NHB","github-pr-description","Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002Fcrates\u002Ffurcode_repo\u002Fsrc\u002Fskills\u002Fgithub-pr-description\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79Y81NKPN89FVB8WFEB8CK8","execute-plan","Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans\u002F{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002Fcrates\u002Ffurcode_repo\u002Fsrc\u002Fskills\u002Fexecute-plan\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79Y7XX5YEY5MWSPZ85SC7E0","create-skill","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002Fcrates\u002Ffurcode_repo\u002Fsrc\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79Y7WKSM87WJSSMEGAAG91B","test-skill","A test skill with resources","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002Fcrates\u002Ffurcode_repo\u002Fsrc\u002Ffixtures\u002Fskills_with_resources\u002Ftest-skill\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79Y7VMME7JNE2S5VAXNKYKJ","minimal-skill","A minimal skill with no resources","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002Fcrates\u002Ffurcode_repo\u002Fsrc\u002Ffixtures\u002Fskills_with_resources\u002Fminimal-skill\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79Y7M0XEE722K3TYGFSGWMX","test-reasoning","Validate that reasoning parameters are correctly serialized and sent to provider APIs. Use when the user asks to test reasoning serialization, run reasoning tests, verify reasoning config fields, or check that ReasoningConfig maps correctly to provider-specific JSON (OpenRouter, Anthropic, GitHub Copilot, Codex).","https:\u002F\u002Fgithub.com\u002Frizrmd\u002Ffurcode\u002Fblob\u002Fmain\u002F.furcode\u002Fskills\u002Ftest-reasoning\u002FSKILL.md",[],[]]