[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ES4EN817WN76HWHQFH994T":3,"skill-same:01M7ES4EN817WN76HWHQFH994T":46},{"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":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M7ES4EN817WN76HWHQFH994T","release",null,"Bump the version in every manifest, update the changelog, tag main and publish a GitHub release marked latest.","iaserrat\u002Fsoftware-design","iaserrat","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1466476?v=4","01M7ES4AAZFN4N0FW0VTVRXMZE","ismael","01M7ES4ABKBNJ0V0X4BD75GKZR",2,"MIT","https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release\ndescription: Bump the version in every manifest, update the changelog, tag main and publish a GitHub release marked latest.\ndisable-model-invocation: true\n---\n\n# Release\n\nOne version names the whole release. It lives in exactly these places:\n\n- `crates\u002Fsoftware-design\u002FCargo.toml` (`version = \"…\"` under `[package]`; the launcher reads it)\n- `Cargo.lock` (the `software-design` package entry; cargo rewrites it)\n- `.claude-plugin\u002Fplugin.json`, `.codex-plugin\u002Fplugin.json`, `package.json` (`\"version\"`)\n- `CHANGELOG.md` (a `## X.Y.Z` heading)\n\nThe internal crates (`history`, `rules`, `syntax`) stay at `0.0.0`: they are unpublished. `tests\u002Ftidy.rs::every_version_names_the_same_release` enforces the manifests agree.\n\n## 1. Preconditions\n\nStop and tell the user if any fails:\n\n- `git status --porcelain` is empty and the branch is `main`.\n- `git fetch origin && git status -sb` shows main is not behind `origin\u002Fmain`.\n- `gh auth status` succeeds.\n\n## 2. Propose the bump\n\n- Current version: from `crates\u002Fsoftware-design\u002FCargo.toml`.\n- Last release: `git describe --tags --abbrev=0` (none yet → everything since the first commit).\n- Read `git log \u003Clast-tag>..HEAD --oneline` and the diff stat. Classify:\n  - **major**: removed or renamed skill\u002Fagent\u002FMCP tool\u002FCLI flag, changed JSON output schema (`SCHEMA_VERSION`), changed hook behavior users rely on. While on `0.x`, a breaking change bumps **minor**.\n  - **minor**: new rule, skill, agent, tool, language or option.\n  - **patch**: fixes, docs, internal refactors only.\n- Ask the user with AskUserQuestion: options patch \u002F minor \u002F major, each label showing the resulting version, the recommended one first with \"(Recommended)\" and a one-line reason drawn from the commits. Do not continue without an answer.\n\n## 3. Bump\n\n1. Replace the old version with the new one in the three JSON manifests and in `crates\u002Fsoftware-design\u002FCargo.toml` (the `[package]` `version` line only — never dependency versions).\n2. Add `## X.Y.Z` at the top of `CHANGELOG.md` (under `# Changelog`), with terse bullets in the existing style summarising user-visible changes since the last tag. Show it to the user and apply their edits.\n3. Run the CI checks; they also refresh `Cargo.lock`:\n   ```bash\n   cargo fmt --all --check && cargo clippy --workspace --all-targets -- -D warnings && cargo test --workspace\n   ```\n4. Confirm alignment: `git grep -n \"X.Y.Z\"` lists every file above, and `git diff --stat` touches nothing else besides `Cargo.lock`.\n\n## 4. Commit, tag, push\n\nShow the diff and get an explicit yes before pushing.\n\n```bash\ngit commit -am \"Release X.Y.Z\"\ngit tag -a vX.Y.Z -m \"X.Y.Z\"\ngit push origin main vX.Y.Z\n```\n\n## 5. GitHub release\n\nNotes are the `## X.Y.Z` section of `CHANGELOG.md` (without the heading):\n\n```bash\nawk '\u002F^## \u002F{p = ($2 == \"X.Y.Z\"); next} p' CHANGELOG.md > \"$TMPDIR\u002Fnotes.md\"\ngh release create vX.Y.Z --verify-tag --title \"X.Y.Z\" --notes-file \"$TMPDIR\u002Fnotes.md\" --latest\n```\n\nThen `gh release list --json tagName,isLatest --jq '.[] | select(.isLatest) | .tagName'` must print `vX.Y.Z`; give the user the URL from `gh release view vX.Y.Z --json url`.\n","# Release\n\nOne version names the whole release. It lives in exactly these places:\n\n- `crates\u002Fsoftware-design\u002FCargo.toml` (`version = \"…\"` under `[package]`; the launcher reads it)\n- `Cargo.lock` (the `software-design` package entry; cargo rewrites it)\n- `.claude-plugin\u002Fplugin.json`, `.codex-plugin\u002Fplugin.json`, `package.json` (`\"version\"`)\n- `CHANGELOG.md` (a `## X.Y.Z` heading)\n\nThe internal crates (`history`, `rules`, `syntax`) stay at `0.0.0`: they are unpublished. `tests\u002Ftidy.rs::every_version_names_the_same_release` enforces the manifests agree.\n\n## 1. Preconditions\n\nStop and tell the user if any fails:\n\n- `git status --porcelain` is empty and the branch is `main`.\n- `git fetch origin && git status -sb` shows main is not behind `origin\u002Fmain`.\n- `gh auth status` succeeds.\n\n## 2. Propose the bump\n\n- Current version: from `crates\u002Fsoftware-design\u002FCargo.toml`.\n- Last release: `git describe --tags --abbrev=0` (none yet → everything since the first commit).\n- Read `git log \u003Clast-tag>..HEAD --oneline` and the diff stat. Classify:\n  - **major**: removed or renamed skill\u002Fagent\u002FMCP tool\u002FCLI flag, changed JSON output schema (`SCHEMA_VERSION`), changed hook behavior users rely on. While on `0.x`, a breaking change bumps **minor**.\n  - **minor**: new rule, skill, agent, tool, language or option.\n  - **patch**: fixes, docs, internal refactors only.\n- Ask the user with AskUserQuestion: options patch \u002F minor \u002F major, each label showing the resulting version, the recommended one first with \"(Recommended)\" and a one-line reason drawn from the commits. Do not continue without an answer.\n\n## 3. Bump\n\n1. Replace the old version with the new one in the three JSON manifests and in `crates\u002Fsoftware-design\u002FCargo.toml` (the `[package]` `version` line only — never dependency versions).\n2. Add `## X.Y.Z` at the top of `CHANGELOG.md` (under `# Changelog`), with terse bullets in the existing style summarising user-visible changes since the last tag. Show it to the user and apply their edits.\n3. Run the CI checks; they also refresh `Cargo.lock`:\n   ```bash\n   cargo fmt --all --check && cargo clippy --workspace --all-targets -- -D warnings && cargo test --workspace\n   ```\n4. Confirm alignment: `git grep -n \"X.Y.Z\"` lists every file above, and `git diff --stat` touches nothing else besides `Cargo.lock`.\n\n## 4. Commit, tag, push\n\nShow the diff and get an explicit yes before pushing.\n\n```bash\ngit commit -am \"Release X.Y.Z\"\ngit tag -a vX.Y.Z -m \"X.Y.Z\"\ngit push origin main vX.Y.Z\n```\n\n## 5. GitHub release\n\nNotes are the `## X.Y.Z` section of `CHANGELOG.md` (without the heading):\n\n```bash\nawk '\u002F^## \u002F{p = ($2 == \"X.Y.Z\"); next} p' CHANGELOG.md > \"$TMPDIR\u002Fnotes.md\"\ngh release create vX.Y.Z --verify-tag --title \"X.Y.Z\" --notes-file \"$TMPDIR\u002Fnotes.md\" --latest\n```\n\nThen `gh release list --json tagName,isLatest --jq '.[] | select(.isLatest) | .tagName'` must print `vX.Y.Z`; give the user the URL from `gh release view vX.Y.Z --json url`.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","a8f011c9435defbcd56579e692b2622e054fd949",".claude\u002Fskills\u002Frelease",0,"https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design","https:\u002F\u002Fiaserrat.github.io\u002Fsoftware-design\u002F","https:\u002F\u002Fgithub.com\u002Fiaserrat","2026-10-16 06:36:47",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add iaserrat\u002Fsoftware-design --skill release",{"tool":39,"command":40},"bunx","bunx skills add iaserrat\u002Fsoftware-design --skill release",{"tool":42,"command":43},"pnpm","pnpm dlx skills add iaserrat\u002Fsoftware-design --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7ES5JTTF604G9E265WCBH4Z","review","Reviews code for design red flags, such as shallow modules, pass-through methods, information leakage, repeated code, comments that repeat code, vague names and ignored errors, and tests whether public interfaces can be used without reading their implementation. Ranks findings by how often the code changes and verifies each against the rule's own exemptions. Use when the user asks to review a diff, branch, pull request, file or directory for design quality, complexity or maintainability, asks whether code is well designed, or asks whether an API, class or module is clear or usable without reading its code.","https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7ES5DPF9SW53SSYFDHXVQS4","perf","Make code faster without making it more complex. Measures before changing anything, looks for a fundamental fix first, and otherwise redesigns around the critical path with special cases moved off it. Use when the user asks to optimise, speed up, or reduce the latency, allocations or memory of code, or to review a change made for performance. Use it even when the user names a specific micro-optimisation, because measuring comes first.","https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002Fskills\u002Fperf\u002FSKILL.md",[],[],{"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},"01M7ES57J7EY0EHG0JCWC8X14M","document","Write or improve the interface and implementation comments of a module. Comments carry what the code cannot say (units, boundaries, invariants, errors, reasons) and never repeat the code. A comment that is hard to write is reported as a design problem. Use when the user asks to document, comment or explain a module, class, function or API, to fix poor or outdated comments, or when the software-design hooks report comments that repeat the code. Use it even when the user only asks to add comments or docstrings.","https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002Fskills\u002Fdocument\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},"01M7ES4Z9E0W4DBSB0QNG3AXE4","design","Designs the interface of a new class, module, API, service or feature before its code is written. Lists the knowledge the module hides, designs three competing interfaces in parallel, tests each on a reader who has never seen the code, compares the caller code each needs, and writes interface comments first. Use whenever the user asks to design, sketch, shape, structure or plan a class, module, API, interface or service, asks which methods or signatures something should have, wants to compare designs, or says \"design it twice\", even when they only describe what the code must do. Typical requests include \"design the class interface\", \"what methods should this class have\", \"how should I structure this module\", \"sketch an API for\", \"design X before I write it\", or any description of a class, module or API that does not exist yet.","https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\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},"01M7ES4QYA6KW2T309B4NJVWVK","change","Plan a change to existing code strategically. Before editing, works out what the code would look like had it been designed with this change in mind, compares that with the smallest patch, and lets the user choose. After editing, checks the diff for red flags and stale comments. Use when the user asks to add a feature to, fix, or extend existing code and the change adds a parameter, flag, special case or exception, touches a module's interface, or spreads across several files. Use it even when the request sounds like a small patch, because small patches are how complexity accumulates.","https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002Fskills\u002Fchange\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},"01M7ES4HJGCDAN3SHZTST77KXX","audit","Audit a whole repository or a large directory for design complexity. Ranks red flags by how often each file changes, verifies candidates against each rule's exemptions in parallel, has a cold reader judge the interfaces of the most-changed modules, and returns the investments worth making first. Use when the user asks for an audit, a design or complexity review of an entire codebase or package, a hotspot map, or where design work would pay off most. Use it even when the user only asks where the code is worst or what to clean up first.","https:\u002F\u002Fgithub.com\u002Fiaserrat\u002Fsoftware-design\u002Fblob\u002Fmain\u002Fskills\u002Faudit\u002FSKILL.md",[],[]]