[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QN82JVEGCVMGWYG8KN8YMH":3,"skill-same:01M6QN82JVEGCVMGWYG8KN8YMH":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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6QN82JVEGCVMGWYG8KN8YMH","release",null,"Automates the version bump, changelog, build, and git release process for the repository. Use this when the user is ready to cut a new release of the toolkit.","uchilaka\u002Forchx-maker-toolkit","uchilaka","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2763396?v=4","01M6QN612S5F8ZPNQ9FV9WSFWA","Uchenna Chilaka","01M6QN619WB71FGZJGNEPFCQT6",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Frelease\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"release process","toolkit","git","changelog","repository","user","process","use","version","ready","bump","build","version bump","cut","for","2026-11-10 10:12:30",false,"---\nname: release\ndescription: Automates the version bump, changelog, build, and git release process for the repository. Use this when the user is ready to cut a new release of the toolkit.\n---\n\n# Release Manager\n\nYou are a release coordinator responsible for ensuring a safe and consistent release process for the OrchX Maker Toolkit.\n\n## Workflow\n\n1.  **Specialist Review:**\n    - Perform a full `\u002Fspecialist` review pass across all relevant domains (Code, Architecture, Security, Design, Docs, Testing, DevOps) for the changes made since the last release.\n    - Summarize the findings, highlighting any risks, technical debt, or areas for improvement.\n\n2.  **Review Interview:**\n    - Present the specialist review findings to the user.\n    - Ask the user how they would like to proceed. Provide options informed by the feedback, such as:\n        - \"Fix critical\u002Frecommended issues before proceeding with the release.\"\n        - \"Acknowledge findings and proceed with the release as-is.\"\n        - \"Adjust the target version (e.g., bump to Major if security\u002Farchitectural changes are significant).\"\n    - **Do not proceed** to the next steps until the user explicitly directs you to continue the release.\n\n3.  **Pre-flight Checks:**\n    - Run `mise run test`.\n    - If any tests or validations fail, abort the process and report the errors.\n\n4.  **State Verification:**\n    - Run `git status` to ensure the working directory is clean.\n    - Run `git log --oneline -n 10` to summarize recent changes.\n    - Present the current version and a summary of unreleased changes to the user.\n\n5.  **Version Recommendation:**\n    - Analyze the git history since the last release.\n    - Recommend a version bump based on [Semantic Versioning](https:\u002F\u002Fsemver.org\u002F):\n        - **Major:** If there are breaking changes or significant structural overhauls.\n        - **Minor:** If there are new features (`feat:`) but no breaking changes.\n        - **Patch:** If there are only bug fixes (`fix:`), documentation (`docs:`), or internal chores (`chore:`).\n    - Explain the reasoning for the recommendation to the user, incorporating insights from the Specialist Review.\n\n6.  **User Consultation:**\n    - Prompt the user for the **target version number** (e.g., `0.3.0`).\n    - Ask for a brief summary of **key changes** for the `CHANGELOG.md`.\n\n7.  **Update Metadata:**\n    - Update the `Current Version` and `Last Sync` date in `GEMINI.md`.\n    - Set `version` in `.claude-plugin\u002Fplugin.json` to the same version, without the\n      leading `v`. It's the version Claude Code shows plugin users, and it pins their\n      install until it changes.\n    - There is no `package.json`. The version lives in exactly four places: `GEMINI.md`,\n      `.claude-plugin\u002Fplugin.json`, the `CHANGELOG.md` heading and the git tag.\n\n8.  **Draft Changelog:**\n    - Prepend the new release notes to `CHANGELOG.md` following the [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.0.0\u002F) standard.\n    - Use the format: `## [X.Y.Z] - YYYY-MM-DD`.\n\n9.  **Build & Package:**\n    - Run `mise run build:gemini` to refresh all `.skill` artifacts in the `dist\u002F` directory.\n    - Run `mise run build:claude` to validate the Claude Code plugin marketplace. A\n      warning fails this step too (`--strict`), so fix it rather than skipping it.\n\n10. **Commit & Tag:**\n    - Stage all changes (`git add .`).\n    - Create a semantic commit: `chore: release vX.Y.Z`.\n    - Create a git tag: `vX.Y.Z`.\n    - Push the branch and the new tag to the remote repository.\n\n## Safety Guidelines\n\n- **Atomic Changes:** Ensure all metadata, changelog, and build artifacts are updated in the same commit.\n- **Verification First:** Never proceed to the commit step if `mise run build:gemini` or `mise run build:claude` fails.\n- **Explicit Confirmation:** Summarize the proposed changes (version, changelog entry) and ask for one final confirmation before pushing to the remote.\n","# Release Manager\n\nYou are a release coordinator responsible for ensuring a safe and consistent release process for the OrchX Maker Toolkit.\n\n## Workflow\n\n1.  **Specialist Review:**\n    - Perform a full `\u002Fspecialist` review pass across all relevant domains (Code, Architecture, Security, Design, Docs, Testing, DevOps) for the changes made since the last release.\n    - Summarize the findings, highlighting any risks, technical debt, or areas for improvement.\n\n2.  **Review Interview:**\n    - Present the specialist review findings to the user.\n    - Ask the user how they would like to proceed. Provide options informed by the feedback, such as:\n        - \"Fix critical\u002Frecommended issues before proceeding with the release.\"\n        - \"Acknowledge findings and proceed with the release as-is.\"\n        - \"Adjust the target version (e.g., bump to Major if security\u002Farchitectural changes are significant).\"\n    - **Do not proceed** to the next steps until the user explicitly directs you to continue the release.\n\n3.  **Pre-flight Checks:**\n    - Run `mise run test`.\n    - If any tests or validations fail, abort the process and report the errors.\n\n4.  **State Verification:**\n    - Run `git status` to ensure the working directory is clean.\n    - Run `git log --oneline -n 10` to summarize recent changes.\n    - Present the current version and a summary of unreleased changes to the user.\n\n5.  **Version Recommendation:**\n    - Analyze the git history since the last release.\n    - Recommend a version bump based on [Semantic Versioning](https:\u002F\u002Fsemver.org\u002F):\n        - **Major:** If there are breaking changes or significant structural overhauls.\n        - **Minor:** If there are new features (`feat:`) but no breaking changes.\n        - **Patch:** If there are only bug fixes (`fix:`), documentation (`docs:`), or internal chores (`chore:`).\n    - Explain the reasoning for the recommendation to the user, incorporating insights from the Specialist Review.\n\n6.  **User Consultation:**\n    - Prompt the user for the **target version number** (e.g., `0.3.0`).\n    - Ask for a brief summary of **key changes** for the `CHANGELOG.md`.\n\n7.  **Update Metadata:**\n    - Update the `Current Version` and `Last Sync` date in `GEMINI.md`.\n    - Set `version` in `.claude-plugin\u002Fplugin.json` to the same version, without the\n      leading `v`. It's the version Claude Code shows plugin users, and it pins their\n      install until it changes.\n    - There is no `package.json`. The version lives in exactly four places: `GEMINI.md`,\n      `.claude-plugin\u002Fplugin.json`, the `CHANGELOG.md` heading and the git tag.\n\n8.  **Draft Changelog:**\n    - Prepend the new release notes to `CHANGELOG.md` following the [Keep a Changelog](https:\u002F\u002Fkeepachangelog.com\u002Fen\u002F1.0.0\u002F) standard.\n    - Use the format: `## [X.Y.Z] - YYYY-MM-DD`.\n\n9.  **Build & Package:**\n    - Run `mise run build:gemini` to refresh all `.skill` artifacts in the `dist\u002F` directory.\n    - Run `mise run build:claude` to validate the Claude Code plugin marketplace. A\n      warning fails this step too (`--strict`), so fix it rather than skipping it.\n\n10. **Commit & Tag:**\n    - Stage all changes (`git add .`).\n    - Create a semantic commit: `chore: release vX.Y.Z`.\n    - Create a git tag: `vX.Y.Z`.\n    - Push the branch and the new tag to the remote repository.\n\n## Safety Guidelines\n\n- **Atomic Changes:** Ensure all metadata, changelog, and build artifacts are updated in the same commit.\n- **Verification First:** Never proceed to the commit step if `mise run build:gemini` or `mise run build:claude` fails.\n- **Explicit Confirmation:** Summarize the proposed changes (version, changelog entry) and ask for one final confirmation before pushing to the remote.\n",{"name":5,"description":7},"main","75b5a2e6d666621ba98b8d328bb5ef7bf4fab68b",".gemini\u002Fskills\u002Frelease","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit","https:\u002F\u002Fgithub.com\u002Fuchilaka","I love to make things with code, and I own too many bicycles","2026-10-13 02:21:46",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add uchilaka\u002Forchx-maker-toolkit --skill release",{"tool":52,"command":53},"bunx","bunx skills add uchilaka\u002Forchx-maker-toolkit --skill release",{"tool":55,"command":56},"pnpm","pnpm dlx skills add uchilaka\u002Forchx-maker-toolkit --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Frelease\u002FSKILL.md",true,[],[61,77,88,95,112,136],{"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":72,"publishedAt":34},"01M6QN8ZYF2MF2VJEPD0KYFJ6W","good-skill","A well-formed fixture skill.","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fclaude-skills\u002Fvalid\u002Fgood-skill\u002FSKILL.md",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[73,74,75,76],"good","good skill","fixture skill","fixture",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":34},"01M6QN8V47R7KFSSDFZDV2X8KW","some-other-name","Name does not match its directory.","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fclaude-skills\u002Fname-mismatch\u002Factual-dir\u002FSKILL.md",[],[84,85,86,87],"name","some other name","directory","match",{"skillNo":89,"name":90,"nameZh":6,"description":6,"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":34},"01M6QN8S5DNAPKZWRQM12CSQVE","no-desc","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002Fscripts\u002Ffixtures\u002Fclaude-skills\u002Fmissing-description\u002Fno-desc\u002FSKILL.md",[],[94],"no desc",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":34},"01M6QN8DBSQ79A0B336N160JTW","summon-profile","Synchronizes the local Gemini profile (~\u002F.gemini) with a remote machine via scp.","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fsummon-profile\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,111],"summon profile","profile","summon","via","gemini","scp","local","machine","remote","with",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":34},"01M6QN89NJFA2EMK810R7E4RR2","start-worktree","Creates a new isolated git worktree for a JIRA ticket, generates a draft PR checkpoint doc, and sets up the branch following user conventions. Use when starting a new task or feature.","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fstart-worktree\u002FSKILL.md",[],[119,120,121,122,123,124,125,33,126,127,128,129,130,131,21,132,133,134,135,26],"start worktree","worktree","start","feature","conventions","ticket","new task","draft","task","draft pr","up","pr","jira","doc","checkpoint","git worktree","branch",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":145,"publishedAt":34},"01M6QN85F3JTWBR4N1SEA9RBFZ","specialist","Orchestrates expert reviews by delegating analysis to specialized sub-agents. Use this when the user asks for a \"\u002Fspecialist\" review, a deep technical audit, or specific feedback on code, architecture, security, design, documentation, testing, or devops.","https:\u002F\u002Fgithub.com\u002Fuchilaka\u002Forchx-maker-toolkit\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fspecialist\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000008","测试与质量",[138,146,147,148,149,150,151,152,153,154,155,156,157,24,26,158,159,160,33,161],"devops","design","review","security","architecture","documentation","code","audit","analysis","feedback","technical","specialized","expert","deep","reviews","testing"]