[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5GMR48HD8KMH9GMP1WRJD":3,"skill-same:01M7F5GMR48HD8KMH9GMP1WRJD":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F5GMR48HD8KMH9GMP1WRJD","release",null,"Ship a new version of the Codealong Mac app. Picks the version, writes the release notes, tags it so GitHub builds, signs and notarizes it, checks the draft as a download gets it, and publishes it once the user says so; installed copies, the website's Download and the Homebrew cask then follow by themselves. Use when the user says they're ready to release, wants a new version out, or runs \u002Frelease (optionally with a version, \u002Frelease 0.4.0).","codealong\u002Fcodealong","codealong","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2642587?v=4","01M7F5GCRMWEV8YSV1TC8DME1V","Codealong","01M7F5GCSA5ECSNV47JZY7X6RW",65,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: release\ndescription: Ship a new version of the Codealong Mac app. Picks the version, writes the release notes, tags it so GitHub builds, signs and notarizes it, checks the draft as a download gets it, and publishes it once the user says so; installed copies, the website's Download and the Homebrew cask then follow by themselves. Use when the user says they're ready to release, wants a new version out, or runs \u002Frelease (optionally with a version, \u002Frelease 0.4.0).\n---\n\n# Release\n\nA release is a version tag on `main`. `scripts\u002Fversion.sh` makes it: it sets the one version the\napp, the `codealong` command and the Claude Code plugin share, commits \"Release x.y.z\" and tags it\nwith the release notes as the tag's message. Pushing the tag has GitHub build the release\n(`.github\u002Fworkflows\u002Frelease.yml`): universal, signed with the Developer ID, notarized, with the\nsigned update and `latest.json`, as a draft release. Publishing the draft is what makes it live:\ninstalled copies find it (their updater reads `releases\u002Flatest\u002Fdownload\u002Flatest.json`), the\nwebsite's Download buttons follow `releases\u002Flatest`, and `.github\u002Fworkflows\u002Fhomebrew.yml` points\nthe cask in `codealong\u002Fhomebrew-tap` at it. `design\u002Fplans\u002Freleases.md` has the decisions behind\nall of it.\n\nEverything a release does is public and can't be taken back once people have it. The user says\ngo at four points, in chat, and you never go past one without it:\n\n1. the version and the notes, before the tag is pushed;\n2. the build, which waits for their approval on GitHub (the `release` environment's reviewer);\n3. publishing the draft;\n4. deleting or moving any tag or release.\n\n## 1. Where things stand\n\n```bash\ngit fetch -q origin\ngit describe --tags --abbrev=0 origin\u002Fmain          # the last version tag\ngh release list -R codealong\u002Fcodealong --limit 5     # drafts waiting, the latest published\ngit rev-parse origin\u002Fmain                            # the commit the release will tag\ngh run list -R codealong\u002Fcodealong --workflow linux.yml --branch main --limit 1 --json headSha,status,conclusion,url   # main's last Linux check\n```\n\nSay what's there: the last release and whether it's published, any draft still waiting (a draft\nolder than `main` is stale: offer to delete it, with its tag, once the new one is out), and\nwhether `main` is green. Something already wrong on `main` is fixed and landed first, the usual\nway (CLAUDE.md's *Landing work*), not in the release.\n\nLinux is checked only every four hours (`linux.yml`), and no Mac can check it, so its last run is\noften of an older commit than the one being released. A release needs a run that passed on the\ncommit it's made from: when the last run's `headSha` isn't `origin\u002Fmain`'s, start one (`gh\nworkflow run linux.yml -R codealong\u002Fcodealong --ref main` prints its link, which ends in its id)\nand wait for it in the background (`gh run watch \u003Cid> -R codealong\u002Fcodealong --exit-status`)\nwhile you write the notes. It takes about three minutes, twenty when its cache is cold; the\nfour-hourly run cancels one still going on `main`, and is then the one to wait for. One that\nfails is fixed and landed like anything else wrong on `main`, and checked again on the commit\nwith the fix.\n\n## 2. The version and the notes\n\nThe version is `x.y.z`: while it's 0.x, a minor version when there are features, a patch when\nthere are only fixes; `x.y.z-beta.n` for a prerelease, which GitHub marks as one, so publishing it\nmoves neither `latest` (installed copies) nor the cask. It must be newer than the app's\n(`src-tauri\u002Ftauri.conf.json`), and a version is never used twice. Take the one the user gave, or\npropose one.\n\nWrite the notes from what changed since the last tag:\n\n```bash\ngit log --no-merges --format='%h %s' \u003Clast tag>..origin\u002Fmain\ngh release view \u003Clast tag> -R codealong\u002Fcodealong --json body --jq .body   # the last notes, for their shape\n```\n\nCommit subjects here are long feature sentences; the notes are for people using the app, not\nfor the repo. Leave out \"Release …\" commits, \"After Codex's review\" follow-ups (they're part of\nthe feature before them), docs, tests, previews and refactors nobody can see. Then, in a file in\nyour scratchpad:\n\n- a first line that says what this version is about, in a sentence;\n- **What's new**: one bullet per feature, a short phrase first and then what it does, plain words\n  and sentence case, the biggest first;\n- **Fixes**, when there are any worth naming;\n- for the first public release only, an **Install** section: the disk image from the release\n  page, or `brew install --cask codealong\u002Ftap\u002Fcodealong`.\n\nThe notes go on the release page and in `latest.json`, which the app shows beside Restart when it\noffers the update, so keep them to what a user would care about. They're public: no names from\nthe owner's other work or this Mac's real projects, people or sessions (the pre-push hook checks\ncommits, not the tag's message, so this is on you).\n\nShow the user the version and the notes, and change them until they say go.\n\n## 3. Tag it\n\nFrom a worktree of its own at `origin\u002Fmain`, never the main checkout, which other sessions'\nuncommitted edits may be in (`version.sh` refuses to run anywhere HEAD isn't `origin\u002Fmain` or\nsomething's uncommitted):\n\n```bash\ngit worktree add --detach ..\u002Fcodealong-release-\u003Cversion> origin\u002Fmain\ncd ..\u002Fcodealong-release-\u003Cversion>\ngit rev-parse HEAD                                   # the commit Linux passed on in step 1\nscripts\u002Fversion.sh \u003Cversion> --notes \u003Cnotes file> --push\n```\n\nWhen `main` has moved past the commit Linux passed on, check the new one as step 1 does before\nrunning `version.sh`, which makes the release from whatever `origin\u002Fmain` is.\n\nIt commits \"Release \u003Cversion>\", tags `v\u003Cversion>`, and pushes the commit to `main` and then the\ntag. When the push of the commit is turned away because `main` moved, nothing reached GitHub:\nthe tag is `version.sh`'s own, only in this worktree, and goes with it (`git tag -d v\u003Cversion>`;\nthe rule about tags is for ones GitHub has), and this step starts again from a fresh worktree.\nWhen the commit went and the tag didn't, push the tag: `git push origin v\u003Cversion>`. Once the\ntag is pushed, from the main checkout:\n\n```bash\nscripts\u002Fcatch-up-main.sh\ngit worktree remove ..\u002Fcodealong-release-\u003Cversion>\n```\n\n## 4. The build\n\n```bash\ngit rev-parse 'v\u003Cversion>^{commit}'\ngh run list -R codealong\u002Fcodealong --workflow release.yml --branch v\u003Cversion> --event push --json databaseId,url,status,headSha\n```\n\nThe run is the one for the tag (a tag's push is its branch here) whose `headSha` is the tagged\ncommit; it can take a minute to appear, so look again rather than take another release's run.\nIt waits for the user's approval before it starts (\"Review deployments\" on its page). Give\nthem the run's link and ask them to approve it there. Approve it yourself only when they tell you\nto in chat, as them, through\n`gh api repos\u002Fcodealong\u002Fcodealong\u002Factions\u002Fruns\u002F\u003Cid>\u002Fpending_deployments`\n(POST `environment_ids[]` from a GET of the same, `state=approved`, a comment).\n\nOnce approved it takes about half an hour, most of it Apple's notarization. Wait for it in the\nbackground (`gh run watch \u003Cid> -R codealong\u002Fcodealong --exit-status`). When it fails:\n\n- `gh run view \u003Cid> -R codealong\u002Fcodealong --log-failed` says where.\n- A step that timed out or Apple's service turning a request away is worth one rerun:\n  `gh run rerun \u003Cid> -R codealong\u002Fcodealong --failed`.\n- A fault in the build or the code is fixed and landed the usual way; the tag then names a\n  commit without the fix, so the release goes out as the next version (a tag is never moved\n  without the user's word).\n- With GitHub's runners down, the same release builds on a Mac with the keys:\n  `scripts\u002Frelease.sh --draft` from the tagged commit, with the keys from 1Password\n  (`design\u002Fplans\u002Freleases.md`).\n\n## 5. Check the draft\n\n```bash\nscripts\u002Fcheck-release.sh \u003Cversion>\n```\n\nIt downloads the draft as GitHub serves it, marks it as downloaded the way a browser does, and\nchecks every file, Gatekeeper and notarization, the signature and entitlements, the version, the\nlicense files, and the update and `latest.json`. Every line must be ok.\n\nIt takes about a minute, most of it the download. One still going after ten minutes is stuck or\nhas a bad network: see what it's waiting on with `ps`, rather than waiting on with it.\n\nWhat it can't check is a person opening it: the first-open prompt, the setup wizard on a first\nrun, the permission prompts. The routine (`design\u002Fplans\u002Freleases.md`) has the user install the\ndraft on a Mac or user account that has never had Codealong before it's published: give them the\ndisk image (`gh release download v\u003Cversion> -R codealong\u002Fcodealong -p Codealong.dmg -D\n\u003Cscratchpad>`) and ask how it went, or have them say they're publishing without trying it, and\nsay which in step 7. On a Mac that also runs Codealong Dev, opening the release quits Dev: they\nshare their settings, and the last one opened wins.\n\n## 6. Publish, when the user says so\n\n```bash\ngh release edit v\u003Cversion> -R codealong\u002Fcodealong --draft=false --latest\n```\n\nA prerelease is published with `--prerelease` and without `--latest`, and then only its own page\nchanges: `latest.json` and the website's Download stay on the last release, and homebrew.yml's run\nskips it by design, leaving the cask where it was. Check those stayed put. A release goes\neverywhere; check that it did:\n\n```bash\ncurl -sL https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Freleases\u002Flatest\u002Fdownload\u002Flatest.json | jq -r .version   # installed copies\ncurl -sI https:\u002F\u002Fwww.codealong.com\u002Fapi\u002Fupdate\u002Fdarwin\u002Faarch64\u002F0.0.0 | grep -i '^location'   # where they ask first: redirects to that latest.json (a HEAD isn't counted)\ncurl -sIL -o \u002Fdev\u002Fnull -w '%{http_code}\\n' https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Freleases\u002Flatest\u002Fdownload\u002FCodealong.dmg   # the website's Download: 200\ngh run list -R codealong\u002Fcodealong --workflow homebrew.yml --limit 1   # moved the cask\ngh api repos\u002Fcodealong\u002Fhomebrew-tap\u002Fcontents\u002FCasks\u002Fcodealong.rb --jq .content | base64 -d | grep -E '^  (version|sha256)'\n```\n\nThe cask's `version` is the new one and its `sha256` the disk image's (`Codealong_\u003Cversion>_universal.dmg.sha256`).\nFor a release (not a prerelease), a Homebrew run that skipped or failed leaves the cask on the\nlast version: its log says why, and\n`gh workflow run homebrew.yml -R codealong\u002Fcodealong --ref v\u003Cversion>` runs it again (on the\ntag: it takes the release from the ref it runs on, and its environment only lets `v*` tags in).\n\n## 7. Say how it went\n\nThe release page's link, what `check-release.sh` and the checks after publishing showed, whether\nthe user tried the draft on a fresh install or published without, and what nobody checked yet\n(an installed copy taking the update). Then offer to delete a stale draft and its tag, if step 1\nfound one.\n","# Release\n\nA release is a version tag on `main`. `scripts\u002Fversion.sh` makes it: it sets the one version the\napp, the `codealong` command and the Claude Code plugin share, commits \"Release x.y.z\" and tags it\nwith the release notes as the tag's message. Pushing the tag has GitHub build the release\n(`.github\u002Fworkflows\u002Frelease.yml`): universal, signed with the Developer ID, notarized, with the\nsigned update and `latest.json`, as a draft release. Publishing the draft is what makes it live:\ninstalled copies find it (their updater reads `releases\u002Flatest\u002Fdownload\u002Flatest.json`), the\nwebsite's Download buttons follow `releases\u002Flatest`, and `.github\u002Fworkflows\u002Fhomebrew.yml` points\nthe cask in `codealong\u002Fhomebrew-tap` at it. `design\u002Fplans\u002Freleases.md` has the decisions behind\nall of it.\n\nEverything a release does is public and can't be taken back once people have it. The user says\ngo at four points, in chat, and you never go past one without it:\n\n1. the version and the notes, before the tag is pushed;\n2. the build, which waits for their approval on GitHub (the `release` environment's reviewer);\n3. publishing the draft;\n4. deleting or moving any tag or release.\n\n## 1. Where things stand\n\n```bash\ngit fetch -q origin\ngit describe --tags --abbrev=0 origin\u002Fmain          # the last version tag\ngh release list -R codealong\u002Fcodealong --limit 5     # drafts waiting, the latest published\ngit rev-parse origin\u002Fmain                            # the commit the release will tag\ngh run list -R codealong\u002Fcodealong --workflow linux.yml --branch main --limit 1 --json headSha,status,conclusion,url   # main's last Linux check\n```\n\nSay what's there: the last release and whether it's published, any draft still waiting (a draft\nolder than `main` is stale: offer to delete it, with its tag, once the new one is out), and\nwhether `main` is green. Something already wrong on `main` is fixed and landed first, the usual\nway (CLAUDE.md's *Landing work*), not in the release.\n\nLinux is checked only every four hours (`linux.yml`), and no Mac can check it, so its last run is\noften of an older commit than the one being released. A release needs a run that passed on the\ncommit it's made from: when the last run's `headSha` isn't `origin\u002Fmain`'s, start one (`gh\nworkflow run linux.yml -R codealong\u002Fcodealong --ref main` prints its link, which ends in its id)\nand wait for it in the background (`gh run watch \u003Cid> -R codealong\u002Fcodealong --exit-status`)\nwhile you write the notes. It takes about three minutes, twenty when its cache is cold; the\nfour-hourly run cancels one still going on `main`, and is then the one to wait for. One that\nfails is fixed and landed like anything else wrong on `main`, and checked again on the commit\nwith the fix.\n\n## 2. The version and the notes\n\nThe version is `x.y.z`: while it's 0.x, a minor version when there are features, a patch when\nthere are only fixes; `x.y.z-beta.n` for a prerelease, which GitHub marks as one, so publishing it\nmoves neither `latest` (installed copies) nor the cask. It must be newer than the app's\n(`src-tauri\u002Ftauri.conf.json`), and a version is never used twice. Take the one the user gave, or\npropose one.\n\nWrite the notes from what changed since the last tag:\n\n```bash\ngit log --no-merges --format='%h %s' \u003Clast tag>..origin\u002Fmain\ngh release view \u003Clast tag> -R codealong\u002Fcodealong --json body --jq .body   # the last notes, for their shape\n```\n\nCommit subjects here are long feature sentences; the notes are for people using the app, not\nfor the repo. Leave out \"Release …\" commits, \"After Codex's review\" follow-ups (they're part of\nthe feature before them), docs, tests, previews and refactors nobody can see. Then, in a file in\nyour scratchpad:\n\n- a first line that says what this version is about, in a sentence;\n- **What's new**: one bullet per feature, a short phrase first and then what it does, plain words\n  and sentence case, the biggest first;\n- **Fixes**, when there are any worth naming;\n- for the first public release only, an **Install** section: the disk image from the release\n  page, or `brew install --cask codealong\u002Ftap\u002Fcodealong`.\n\nThe notes go on the release page and in `latest.json`, which the app shows beside Restart when it\noffers the update, so keep them to what a user would care about. They're public: no names from\nthe owner's other work or this Mac's real projects, people or sessions (the pre-push hook checks\ncommits, not the tag's message, so this is on you).\n\nShow the user the version and the notes, and change them until they say go.\n\n## 3. Tag it\n\nFrom a worktree of its own at `origin\u002Fmain`, never the main checkout, which other sessions'\nuncommitted edits may be in (`version.sh` refuses to run anywhere HEAD isn't `origin\u002Fmain` or\nsomething's uncommitted):\n\n```bash\ngit worktree add --detach ..\u002Fcodealong-release-\u003Cversion> origin\u002Fmain\ncd ..\u002Fcodealong-release-\u003Cversion>\ngit rev-parse HEAD                                   # the commit Linux passed on in step 1\nscripts\u002Fversion.sh \u003Cversion> --notes \u003Cnotes file> --push\n```\n\nWhen `main` has moved past the commit Linux passed on, check the new one as step 1 does before\nrunning `version.sh`, which makes the release from whatever `origin\u002Fmain` is.\n\nIt commits \"Release \u003Cversion>\", tags `v\u003Cversion>`, and pushes the commit to `main` and then the\ntag. When the push of the commit is turned away because `main` moved, nothing reached GitHub:\nthe tag is `version.sh`'s own, only in this worktree, and goes with it (`git tag -d v\u003Cversion>`;\nthe rule about tags is for ones GitHub has), and this step starts again from a fresh worktree.\nWhen the commit went and the tag didn't, push the tag: `git push origin v\u003Cversion>`. Once the\ntag is pushed, from the main checkout:\n\n```bash\nscripts\u002Fcatch-up-main.sh\ngit worktree remove ..\u002Fcodealong-release-\u003Cversion>\n```\n\n## 4. The build\n\n```bash\ngit rev-parse 'v\u003Cversion>^{commit}'\ngh run list -R codealong\u002Fcodealong --workflow release.yml --branch v\u003Cversion> --event push --json databaseId,url,status,headSha\n```\n\nThe run is the one for the tag (a tag's push is its branch here) whose `headSha` is the tagged\ncommit; it can take a minute to appear, so look again rather than take another release's run.\nIt waits for the user's approval before it starts (\"Review deployments\" on its page). Give\nthem the run's link and ask them to approve it there. Approve it yourself only when they tell you\nto in chat, as them, through\n`gh api repos\u002Fcodealong\u002Fcodealong\u002Factions\u002Fruns\u002F\u003Cid>\u002Fpending_deployments`\n(POST `environment_ids[]` from a GET of the same, `state=approved`, a comment).\n\nOnce approved it takes about half an hour, most of it Apple's notarization. Wait for it in the\nbackground (`gh run watch \u003Cid> -R codealong\u002Fcodealong --exit-status`). When it fails:\n\n- `gh run view \u003Cid> -R codealong\u002Fcodealong --log-failed` says where.\n- A step that timed out or Apple's service turning a request away is worth one rerun:\n  `gh run rerun \u003Cid> -R codealong\u002Fcodealong --failed`.\n- A fault in the build or the code is fixed and landed the usual way; the tag then names a\n  commit without the fix, so the release goes out as the next version (a tag is never moved\n  without the user's word).\n- With GitHub's runners down, the same release builds on a Mac with the keys:\n  `scripts\u002Frelease.sh --draft` from the tagged commit, with the keys from 1Password\n  (`design\u002Fplans\u002Freleases.md`).\n\n## 5. Check the draft\n\n```bash\nscripts\u002Fcheck-release.sh \u003Cversion>\n```\n\nIt downloads the draft as GitHub serves it, marks it as downloaded the way a browser does, and\nchecks every file, Gatekeeper and notarization, the signature and entitlements, the version, the\nlicense files, and the update and `latest.json`. Every line must be ok.\n\nIt takes about a minute, most of it the download. One still going after ten minutes is stuck or\nhas a bad network: see what it's waiting on with `ps`, rather than waiting on with it.\n\nWhat it can't check is a person opening it: the first-open prompt, the setup wizard on a first\nrun, the permission prompts. The routine (`design\u002Fplans\u002Freleases.md`) has the user install the\ndraft on a Mac or user account that has never had Codealong before it's published: give them the\ndisk image (`gh release download v\u003Cversion> -R codealong\u002Fcodealong -p Codealong.dmg -D\n\u003Cscratchpad>`) and ask how it went, or have them say they're publishing without trying it, and\nsay which in step 7. On a Mac that also runs Codealong Dev, opening the release quits Dev: they\nshare their settings, and the last one opened wins.\n\n## 6. Publish, when the user says so\n\n```bash\ngh release edit v\u003Cversion> -R codealong\u002Fcodealong --draft=false --latest\n```\n\nA prerelease is published with `--prerelease` and without `--latest`, and then only its own page\nchanges: `latest.json` and the website's Download stay on the last release, and homebrew.yml's run\nskips it by design, leaving the cask where it was. Check those stayed put. A release goes\neverywhere; check that it did:\n\n```bash\ncurl -sL https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Freleases\u002Flatest\u002Fdownload\u002Flatest.json | jq -r .version   # installed copies\ncurl -sI https:\u002F\u002Fwww.codealong.com\u002Fapi\u002Fupdate\u002Fdarwin\u002Faarch64\u002F0.0.0 | grep -i '^location'   # where they ask first: redirects to that latest.json (a HEAD isn't counted)\ncurl -sIL -o \u002Fdev\u002Fnull -w '%{http_code}\\n' https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Freleases\u002Flatest\u002Fdownload\u002FCodealong.dmg   # the website's Download: 200\ngh run list -R codealong\u002Fcodealong --workflow homebrew.yml --limit 1   # moved the cask\ngh api repos\u002Fcodealong\u002Fhomebrew-tap\u002Fcontents\u002FCasks\u002Fcodealong.rb --jq .content | base64 -d | grep -E '^  (version|sha256)'\n```\n\nThe cask's `version` is the new one and its `sha256` the disk image's (`Codealong_\u003Cversion>_universal.dmg.sha256`).\nFor a release (not a prerelease), a Homebrew run that skipped or failed leaves the cask on the\nlast version: its log says why, and\n`gh workflow run homebrew.yml -R codealong\u002Fcodealong --ref v\u003Cversion>` runs it again (on the\ntag: it takes the release from the ref it runs on, and its environment only lets `v*` tags in).\n\n## 7. Say how it went\n\nThe release page's link, what `check-release.sh` and the checks after publishing showed, whether\nthe user tried the draft on a fresh install or published without, and what nobody checked yet\n(an installed copy taking the update). Then offer to delete a stale draft and its tag, if step 1\nfound one.\n",{"name":5,"description":7},"main","7e79e28061ba731f68d2a22ae5690f14369d306e",".claude\u002Fskills\u002Frelease",7,"https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong","https:\u002F\u002Fwww.codealong.com","https:\u002F\u002Fgithub.com\u002Fcodealong","Every coding agent you run, in one window. Free and open source, for macOS and Linux.","2026-11-15 13:48:51",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add codealong\u002Fcodealong --skill release",{"tool":39,"command":40},"bunx","bunx skills add codealong\u002Fcodealong --skill release",{"tool":42,"command":43},"pnpm","pnpm dlx skills add codealong\u002Fcodealong --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",true,[],[48,54,60,66],{"skillNo":49,"name":9,"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},"01M7F5GZSWX0WTZYPXDFXGMEW6","Codealong todos, sessions and accounts on this Mac, through the `codealong` command. Use when the user asks for something done with a Codealong todo (adding, starting, changing, finishing) or the session was started on one, when you need to know what other agents or sessions did in this repo, to message one (on any account or harness) or to name one or a todo in a reply (as a link), when you'd have another account, harness or model (Codex, say) review, check or take on part of your work (a helper, started here, not with its own CLI or plugin), when asked to go over the sessions that wait on the user and suggest replies, to run as their orchestrator, to visualize or lay out their sessions on Codealong's canvas, or to make a board of some work or add to one, when asked about a meeting Codealong heard (its transcript or notes), when choosing an account to start something on, or when a task needs a service you have no tool for (Slack, Figma, a mailbox) that another account's MCP servers or connectors may reach.","https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Fblob\u002Fmain\u002Fskills\u002Fcodealong\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"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":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F5GX97JHEJEK0PJB3CXHWV","visualize","https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"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":63,"categories":64,"keywords":65,"publishedAt":19},"01M7F5GW6C8NKPG40KZXHENWFS","orchestrate","https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Forchestrate\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"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":69,"categories":70,"keywords":71,"publishedAt":19},"01M7F5GSS1P702WJT2ZWAVJ7V4","meetings","https:\u002F\u002Fgithub.com\u002Fcodealong\u002Fcodealong\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmeetings\u002FSKILL.md",[],[]]