[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5QTDVXZDTYCB302QA7WAE":3,"skill-same:01M7F5QTDVXZDTYCB302QA7WAE":44},{"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},"01M7F5QTDVXZDTYCB302QA7WAE","remora-prepare-release",null,"Prepare a verified software release, updating CHANGELOG.md, proposing a semantic tag, and generating concise GitHub release notes under the anti-slop standard.","edumarcano\u002Fremora","edumarcano","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271045253?v=4","01M7F5P7E2K8Y0S16FF92W4MXK","Eduardo Marcano","01M7F5P7F8SZKM7YCEPYCD942M",0,"MIT","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-prepare-release\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: remora-prepare-release\ndescription: Prepare a verified software release, updating CHANGELOG.md, proposing a semantic tag, and generating concise GitHub release notes under the anti-slop standard.\n---\n\n# Prepare a release\n\nEstablish the target root and explicitly read `.remora\u002Fstandards\u002Fengineering.md`\nand `.remora\u002Fstandards\u002Fdocumentation.md`, plus applicable root and scoped project\ninstructions. Follow shared reporting rules. Paths are target-root relative.\nMissing resources mean an incomplete installation; report the gap without fetching\nreplacements. Use native host tools without a separate service or runtime.\n\n## Pre-flight hygiene and sanitization\n\nInspect the release branch (defaulting to `main`) and perform a pre-flight sanity\ncheck before drafting release notes:\n\n1. **Working tree clean:** Verify that `git status` has no uncommitted changes,\nuntracked files, or unfinished merges.\n2. **Path and secret sanitization:** Verify that no private environment files\n(`.env`), secrets, or absolute workstation paths (such as `C:\\Users\\...` or personal\nhome directories) are committed in documentation, configuration, or code.\n3. **License check:** Confirm that an approved `LICENSE` file exists in the root.\n4. **Verification status:** Confirm that test and content verification suites pass\ncleanly before releasing.\n\n## Inspect changes and determine version\n\nFind the latest Git tag using `git describe --tags --abbrev=0` (or identify an initial\nfirst release if no tags exist). Inspect all commits since that tag using\n`git log \u003Clast_tag>..HEAD --no-merges`.\n\nAnalyze the changes and recommend the appropriate Semantic Versioning (SemVer) bump:\n- **Patch (0.0.x):** Backwards-compatible bug fixes and documentation updates.\n- **Minor (0.x.0):** New backwards-compatible capabilities or skills.\n- **Major (x.0.0):** Breaking changes to public interfaces or workflows.\n\n## Assemble the three release deliverables\n\nApply the anti-slop editorial standard from `.remora\u002Fstandards\u002Fdocumentation.md`:\nno celebratory fluff (\"We are thrilled to announce\"), no marketing jargon (\"seamless\",\n\"game-changing\"), and no decorative em-dashes. Keep writing direct and active.\n\n### 1. CHANGELOG.md update\nUpdate `CHANGELOG.md` directly in the working tree following *Keep a Changelog* conventions:\n- Use standard categories: `### Added`, `### Changed`, `### Fixed`, `### Removed`.\n- Exclude internal churn, merge commits, and minor typos.\n- Write punchy bullet points describing user-facing capabilities in the present tense.\n- The detailed changelog edits live directly in the working tree diff and are verified\nvia `git diff` or in a PR, rather than duplicated as full text in chat.\n\n### 2. Semantic Git tag\nPresent the proposed Git tag (e.g., `v0.1.0` or `v0.2.0`) and SemVer rationale directly\nin chat.\n\n### 3. GitHub release notes\nPresent the concise GitHub release notes directly in chat:\n- Simpler and punchier than the detailed changelog.\n- 1 to 2 sentences summarizing the release milestone.\n- 3 to 4 key highlights.\n- The 1-line installation or quick-start command.\n\n## Safety and execution boundary\n\nPreparing a release operates within clear boundaries:\n- Preparing the release applies the structured `CHANGELOG.md` edits directly to the\nworking tree for inspection via `git diff`.\n- Present only the pre-flight verification status, proposed tag, and GitHub release\nnotes in the conversation for review.\n- Creating the actual Git tag (`git tag \u003Cversion>`) or publishing via `gh release create`\nrequires explicit user confirmation.\n","# Prepare a release\n\nEstablish the target root and explicitly read `.remora\u002Fstandards\u002Fengineering.md`\nand `.remora\u002Fstandards\u002Fdocumentation.md`, plus applicable root and scoped project\ninstructions. Follow shared reporting rules. Paths are target-root relative.\nMissing resources mean an incomplete installation; report the gap without fetching\nreplacements. Use native host tools without a separate service or runtime.\n\n## Pre-flight hygiene and sanitization\n\nInspect the release branch (defaulting to `main`) and perform a pre-flight sanity\ncheck before drafting release notes:\n\n1. **Working tree clean:** Verify that `git status` has no uncommitted changes,\nuntracked files, or unfinished merges.\n2. **Path and secret sanitization:** Verify that no private environment files\n(`.env`), secrets, or absolute workstation paths (such as `C:\\Users\\...` or personal\nhome directories) are committed in documentation, configuration, or code.\n3. **License check:** Confirm that an approved `LICENSE` file exists in the root.\n4. **Verification status:** Confirm that test and content verification suites pass\ncleanly before releasing.\n\n## Inspect changes and determine version\n\nFind the latest Git tag using `git describe --tags --abbrev=0` (or identify an initial\nfirst release if no tags exist). Inspect all commits since that tag using\n`git log \u003Clast_tag>..HEAD --no-merges`.\n\nAnalyze the changes and recommend the appropriate Semantic Versioning (SemVer) bump:\n- **Patch (0.0.x):** Backwards-compatible bug fixes and documentation updates.\n- **Minor (0.x.0):** New backwards-compatible capabilities or skills.\n- **Major (x.0.0):** Breaking changes to public interfaces or workflows.\n\n## Assemble the three release deliverables\n\nApply the anti-slop editorial standard from `.remora\u002Fstandards\u002Fdocumentation.md`:\nno celebratory fluff (\"We are thrilled to announce\"), no marketing jargon (\"seamless\",\n\"game-changing\"), and no decorative em-dashes. Keep writing direct and active.\n\n### 1. CHANGELOG.md update\nUpdate `CHANGELOG.md` directly in the working tree following *Keep a Changelog* conventions:\n- Use standard categories: `### Added`, `### Changed`, `### Fixed`, `### Removed`.\n- Exclude internal churn, merge commits, and minor typos.\n- Write punchy bullet points describing user-facing capabilities in the present tense.\n- The detailed changelog edits live directly in the working tree diff and are verified\nvia `git diff` or in a PR, rather than duplicated as full text in chat.\n\n### 2. Semantic Git tag\nPresent the proposed Git tag (e.g., `v0.1.0` or `v0.2.0`) and SemVer rationale directly\nin chat.\n\n### 3. GitHub release notes\nPresent the concise GitHub release notes directly in chat:\n- Simpler and punchier than the detailed changelog.\n- 1 to 2 sentences summarizing the release milestone.\n- 3 to 4 key highlights.\n- The 1-line installation or quick-start command.\n\n## Safety and execution boundary\n\nPreparing a release operates within clear boundaries:\n- Preparing the release applies the structured `CHANGELOG.md` edits directly to the\nworking tree for inspection via `git diff`.\n- Present only the pre-flight verification status, proposed tag, and GitHub release\nnotes in the conversation for review.\n- Creating the actual Git tag (`git tag \u003Cversion>`) or publishing via `gh release create`\nrequires explicit user confirmation.\n",{"name":5,"description":7},"main","38d582e28bc537a1f0d2f9009cbe360b533a68a9","skills\u002Fremora-prepare-release","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora","https:\u002F\u002Fgithub.com\u002Fedumarcano","2026-11-02 10:38:08",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add edumarcano\u002Fremora --skill remora-prepare-release",{"tool":36,"command":37},"bunx","bunx skills add edumarcano\u002Fremora --skill remora-prepare-release",{"tool":39,"command":40},"pnpm","pnpm dlx skills add edumarcano\u002Fremora --skill remora-prepare-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-prepare-release\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7F5R689RVZVVTF8BGQY7TWZ","remora-review-change","Review a named implementation, diff, or revision range using independent split-axis analysis with consequence-based blocking. Read-only review never applies repairs.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-review-change\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7F5R098NFBP9HWF7Y9107V7","remora-remediate-project","Orchestrate repository onboarding and cleanup across grounding, documentation sanitization, test protection, and scoped debt remediation through checkpointed review gates.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-remediate-project\u002FSKILL.md",[],[],{"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},"01M7F5QMX7CHP9QPKCF8EA119Z","remora-prepare-pr","Prepare a concise, reviewer-friendly pull request brief adhering to the anti-slop standard, emphasizing artifact proof and reviewer verification over redundant CI logs.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-prepare-pr\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},"01M7F5QFF5Z5XM0EMA8MB5P708","remora-plan-change","Investigate and plan a scoped development change into phased, verifiable work packets using repository evidence, requirements, and acceptance criteria. Planning remains read-only unless saving a plan is requested.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-plan-change\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},"01M7F5QA8C5DKW4FTA71KYYB7Q","remora-implement-plan","Implement an approved plan or clear scoped development request across phased work packets, including checkpoint verification, empirical artifact proof, and split-axis review.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-implement-plan\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},"01M7F5Q4VH87R8KTJJE473XK1T","remora-fix-regression","Diagnose a reported failure or repair a regression through reproduction-first evidence, an explicit fallback protocol, and proportional before\u002Fafter verification. Diagnosis-only requests remain read-only.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-fix-regression\u002FSKILL.md",[],[]]