[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BZF3RPE8A4Z9KMJJBJPCPD":3,"skill-same:01M6BZF3RPE8A4Z9KMJJBJPCPD":56},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6BZF3RPE8A4Z9KMJJBJPCPD","release",null,"Read before any release work — instant builds, nightlies, stable tags, publishing, release workflows — or symbolizing a user's crash log.","clice-io\u002Fclice","clice-io","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F176553789?v=4","01M6BZEJH3SKDZ3SMSS1V6CKKB","clice","01M6BZEJN97S3AQVRQ4V7GGE5C",1383,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27],"work","instant","workflows","read","publishing","tags","crash","user","log","2026-11-10 10:12:30",false,"---\nname: release\ndescription: Read before any release work — instant builds, nightlies, stable tags, publishing, release workflows — or symbolizing a user's crash log.\n---\n\n# Releases\n\n## Versioning\n\nOne version number everywhere: git tag `vX.Y.Z` == extension version == release\npage. Odd minor = pre-release channel, even minor = stable (the VS Code\nMarketplace convention). Nightlies compute `X.\u003Codd>.YYYYMMDDHH` (UTC hour) on the\nodd minor above the newest release — `0.1.*` today, `0.3.*` after stable\n`v0.2.0` — so nobody edits version numbers by hand. The versions in\n`bazel\u002Fworkspace_status.mjs`, `pixi.toml`, and `editors\u002Fvscode\u002Fpackage.json`\nare permanent placeholders (`0.1.0`); the real version is injected from the\ntag at build time (binary via git describe, vsix via CI). A local `vsce publish` with the placeholder is rejected by the\nMarketplace — that is intentional accident protection. Open VSX has no such\nguard: a local `pixi run publish-ovsx` publishes the placeholder version for\nreal, so leave Open VSX to CI.\n\n## Tier 1 — Instant builds (every green CI run)\n\nNothing to operate. Every `main` push and PR run repackages the test-suite\nbinaries (no strip) into `vsix-build-\u003Ctarget>` workflow artifacts, and\nthe raw binaries are in `build-\u003Ctriple>-\u003Ctype>` artifacts. To hand a\nfix to a user: point them at the run's artifact (GitHub login required), or\nhave them set `clice.executable` to the extracted binary.\n\n## Tier 2 — Nightly (pre-release channel)\n\n`nightly.yml` runs daily (cron) or via `gh workflow run nightly.yml`:\nskips when main has no new commits, otherwise tags the nightly version and\n**promotes** — nothing is rebuilt. Every main CI run already packages the\nbinaries its test suites validated (the build jobs build the packages);\nnightly picks the newest main commit whose green run still has live\npackage artifacts (path-filtered runs such as docs-only commits build\nnothing), tags exactly that commit, downloads its packages, attaches them\nto a GitHub pre-release plus the Marketplace and Open VSX pre-release\nchannels, and\nprunes odd-minor pre-releases older than 30 days or beyond the newest 25\n(the Zed extension reads only the first 30 releases, which must keep the\nnewest stable one), sparing the release `mason-org\u002Fmason-registry` pins in\n`packages\u002Fclice\u002Fpackage.yaml` — Mason's Renovate bumps that pin only to\nstable releases. Promotion fails loudly\nif no packaged green run exists. A nightly can tag only a commit whose\n`.github\u002Fworkflows\u002F` are main's: GitHub refuses `GITHUB_TOKEN` any other,\nsince a tag makes its commit's workflows runnable. Every change to them\nbuilds (`main.yml`'s path filter) and every main commit gets a run of its\nown, so the pick lacks them only while that change's `main` run is red or\nstill running; the nightly then fails before tagging, naming the change:\nrerun its run green (`gh run rerun \u003Cid> --failed`), or wait for it. Once tagged, it dispatches the ecosystem\nround (`ecosystem.yml`, `ecosystem\u002FREADME.md`) on that commit with the\npackages' CI run: every real project's regression and perf jobs, report\nonly; perf measures clice against the nightly before (what clice spends a\ntenth more of is listed), on Sundays against clangd. A failed nightly just means no nightly\nthat day — fix main and rerun via dispatch, with the maintainer's\napproval like any release trigger.\n\nEvery GitHub release, nightly or stable, is created as a draft and\npublished by `publish-clice.yml` only once all six platform archives are\nattached: drafts are hidden from anyone without push access, so no user's\neditor extension ever installs from a half-uploaded release. A failed promote job leaves\nthe draft behind; `gh run rerun \u003Cid> --failed` finishes and publishes it.\n\nThe vsix packaging matrix runs in parallel, but release upload and\nregistry publishing happen in one serial job (`publish-release`) with\n5 attempts per vsix — concurrent publishes trip Marketplace internal\nerrors (TF400898). Open VSX (org secret `UPLOAD_VSX_EXT`, namespace\n`clice-io`) publishes the same vsix after the Marketplace step and runs\neven when that step failed, so neither registry blocks the other; it\nchecks the token with `ovsx verify-pat` first and is skipped with a\nnotice when the secret is empty. The job is rerun-safe: `gh run rerun \u003Cid> --failed`\nre-uploads with `--clobber` and skips already-published versions, so a\ntransient registry failure is recovered by rerunning just that job —\nnever by a new tag.\n\nThe binary embeds its build identity (`git describe`: nearest tag + commit\nhash), not the release tag — the tag is applied after the build. Match crash\nlogs to releases by the commit hash; the release notes state the hash.\n\n## Tier 3 — Stable release (manual, even minor)\n\nEvery step that tags or publishes needs the maintainer's explicit approval first.\n\n1. Freeze: stop merging features; the last nightlies of the freeze are the RCs.\n2. When a nightly is judged good — its ecosystem round shows no new\n   failure: every job green, a job whose failures the project already knows\n   (its `known` issues) green too — dispatch its round against clangd and\n   read its perf tables:\n   `gh workflow run ecosystem.yml --ref main -f run=\u003Cits CI run> -f clangd=true`\n   (the round reads the run's `build-*` artifacts, which live three days:\n   for an older nightly, rerun its main workflow first). Then tag its commit:\n   `git tag v0.2.0 \u003Ccommit> && git push origin v0.2.0`.\n   The tag push runs the release path of `main.yml`, which promotes the\n   already-tested packages from that commit's green CI run and publishes the\n   extensions (Marketplace and Open VSX, without the pre-release flag). The promote path\n   creates the GitHub release as a draft if none exists, and publishes it\n   once every platform archive is attached; it refuses a release that is\n   already published, so notes prepared on the releases page beforehand\n   must be saved as a draft. Package artifacts\n   expire 30 days after the CI run, so the tagged commit's run must be\n   less than a month old — for an older commit, rerun its main workflow\n   first to regenerate the packages.\n3. Write the release notes on the GitHub release page (the download table\n   format from the nightly notes is a good template).\n4. Verify: assets present (6 packages + 6 symbol archives + 6 vsix),\n   Marketplace and Open VSX show the new stable version.\n\n## Plumbing changes\n\nThere is no separate dry run: packaging runs on every CI build (the\nplatforms of `test.yml` that package build `\u002F\u002F:package` and `\u002F\u002F:symbols`) and the vsix\npath runs as `instant-vscode`, so release plumbing is exercised by every\ncode-touching PR. Only the promote\u002Fupload glue (`publish-clice.yml`,\nnightly orchestration) is release-time-only.\n\n## Crash log support\n\nAsk the user for the log (the crashed process's `.log` from the session\ndirectory, printed at startup in the editor's clice output panel; by\ndefault `.clice\u002Flogs\u002F\u003Csession>\u002F` in the project, under `logging_dir` when\nthe settings name one). The crash section starts with `clice \u003Cversion>\n\u003Ctarget>` and the link to the commit's source —\ndownload that release's `*.symbols.tar.xz` (`.zip` for Windows; GSYM) and run:\n\n```bash\npython scripts\u002Fsymbolize.py crash.log --symbols clice.gsym\n```\n\nEvery CI platform that packages runs this path on its own package: the package's clice\ncrashes on purpose and its trace symbolizes against the symbol package\n(`scripts\u002Fcheck_crash_symbols.py`).\n\nFor core-dump-level debugging, fetch the full DWARF from the `debug-info-*`\nartifact of the main CI run that built the release (90-day retention; find\nit via the commit hash in the release notes). If the log predates the\nversion line or the release was pruned, symbolization is not possible — ask\nthe user to reproduce on a current nightly.\n","# Releases\n\n## Versioning\n\nOne version number everywhere: git tag `vX.Y.Z` == extension version == release\npage. Odd minor = pre-release channel, even minor = stable (the VS Code\nMarketplace convention). Nightlies compute `X.\u003Codd>.YYYYMMDDHH` (UTC hour) on the\nodd minor above the newest release — `0.1.*` today, `0.3.*` after stable\n`v0.2.0` — so nobody edits version numbers by hand. The versions in\n`bazel\u002Fworkspace_status.mjs`, `pixi.toml`, and `editors\u002Fvscode\u002Fpackage.json`\nare permanent placeholders (`0.1.0`); the real version is injected from the\ntag at build time (binary via git describe, vsix via CI). A local `vsce publish` with the placeholder is rejected by the\nMarketplace — that is intentional accident protection. Open VSX has no such\nguard: a local `pixi run publish-ovsx` publishes the placeholder version for\nreal, so leave Open VSX to CI.\n\n## Tier 1 — Instant builds (every green CI run)\n\nNothing to operate. Every `main` push and PR run repackages the test-suite\nbinaries (no strip) into `vsix-build-\u003Ctarget>` workflow artifacts, and\nthe raw binaries are in `build-\u003Ctriple>-\u003Ctype>` artifacts. To hand a\nfix to a user: point them at the run's artifact (GitHub login required), or\nhave them set `clice.executable` to the extracted binary.\n\n## Tier 2 — Nightly (pre-release channel)\n\n`nightly.yml` runs daily (cron) or via `gh workflow run nightly.yml`:\nskips when main has no new commits, otherwise tags the nightly version and\n**promotes** — nothing is rebuilt. Every main CI run already packages the\nbinaries its test suites validated (the build jobs build the packages);\nnightly picks the newest main commit whose green run still has live\npackage artifacts (path-filtered runs such as docs-only commits build\nnothing), tags exactly that commit, downloads its packages, attaches them\nto a GitHub pre-release plus the Marketplace and Open VSX pre-release\nchannels, and\nprunes odd-minor pre-releases older than 30 days or beyond the newest 25\n(the Zed extension reads only the first 30 releases, which must keep the\nnewest stable one), sparing the release `mason-org\u002Fmason-registry` pins in\n`packages\u002Fclice\u002Fpackage.yaml` — Mason's Renovate bumps that pin only to\nstable releases. Promotion fails loudly\nif no packaged green run exists. A nightly can tag only a commit whose\n`.github\u002Fworkflows\u002F` are main's: GitHub refuses `GITHUB_TOKEN` any other,\nsince a tag makes its commit's workflows runnable. Every change to them\nbuilds (`main.yml`'s path filter) and every main commit gets a run of its\nown, so the pick lacks them only while that change's `main` run is red or\nstill running; the nightly then fails before tagging, naming the change:\nrerun its run green (`gh run rerun \u003Cid> --failed`), or wait for it. Once tagged, it dispatches the ecosystem\nround (`ecosystem.yml`, `ecosystem\u002FREADME.md`) on that commit with the\npackages' CI run: every real project's regression and perf jobs, report\nonly; perf measures clice against the nightly before (what clice spends a\ntenth more of is listed), on Sundays against clangd. A failed nightly just means no nightly\nthat day — fix main and rerun via dispatch, with the maintainer's\napproval like any release trigger.\n\nEvery GitHub release, nightly or stable, is created as a draft and\npublished by `publish-clice.yml` only once all six platform archives are\nattached: drafts are hidden from anyone without push access, so no user's\neditor extension ever installs from a half-uploaded release. A failed promote job leaves\nthe draft behind; `gh run rerun \u003Cid> --failed` finishes and publishes it.\n\nThe vsix packaging matrix runs in parallel, but release upload and\nregistry publishing happen in one serial job (`publish-release`) with\n5 attempts per vsix — concurrent publishes trip Marketplace internal\nerrors (TF400898). Open VSX (org secret `UPLOAD_VSX_EXT`, namespace\n`clice-io`) publishes the same vsix after the Marketplace step and runs\neven when that step failed, so neither registry blocks the other; it\nchecks the token with `ovsx verify-pat` first and is skipped with a\nnotice when the secret is empty. The job is rerun-safe: `gh run rerun \u003Cid> --failed`\nre-uploads with `--clobber` and skips already-published versions, so a\ntransient registry failure is recovered by rerunning just that job —\nnever by a new tag.\n\nThe binary embeds its build identity (`git describe`: nearest tag + commit\nhash), not the release tag — the tag is applied after the build. Match crash\nlogs to releases by the commit hash; the release notes state the hash.\n\n## Tier 3 — Stable release (manual, even minor)\n\nEvery step that tags or publishes needs the maintainer's explicit approval first.\n\n1. Freeze: stop merging features; the last nightlies of the freeze are the RCs.\n2. When a nightly is judged good — its ecosystem round shows no new\n   failure: every job green, a job whose failures the project already knows\n   (its `known` issues) green too — dispatch its round against clangd and\n   read its perf tables:\n   `gh workflow run ecosystem.yml --ref main -f run=\u003Cits CI run> -f clangd=true`\n   (the round reads the run's `build-*` artifacts, which live three days:\n   for an older nightly, rerun its main workflow first). Then tag its commit:\n   `git tag v0.2.0 \u003Ccommit> && git push origin v0.2.0`.\n   The tag push runs the release path of `main.yml`, which promotes the\n   already-tested packages from that commit's green CI run and publishes the\n   extensions (Marketplace and Open VSX, without the pre-release flag). The promote path\n   creates the GitHub release as a draft if none exists, and publishes it\n   once every platform archive is attached; it refuses a release that is\n   already published, so notes prepared on the releases page beforehand\n   must be saved as a draft. Package artifacts\n   expire 30 days after the CI run, so the tagged commit's run must be\n   less than a month old — for an older commit, rerun its main workflow\n   first to regenerate the packages.\n3. Write the release notes on the GitHub release page (the download table\n   format from the nightly notes is a good template).\n4. Verify: assets present (6 packages + 6 symbol archives + 6 vsix),\n   Marketplace and Open VSX show the new stable version.\n\n## Plumbing changes\n\nThere is no separate dry run: packaging runs on every CI build (the\nplatforms of `test.yml` that package build `\u002F\u002F:package` and `\u002F\u002F:symbols`) and the vsix\npath runs as `instant-vscode`, so release plumbing is exercised by every\ncode-touching PR. Only the promote\u002Fupload glue (`publish-clice.yml`,\nnightly orchestration) is release-time-only.\n\n## Crash log support\n\nAsk the user for the log (the crashed process's `.log` from the session\ndirectory, printed at startup in the editor's clice output panel; by\ndefault `.clice\u002Flogs\u002F\u003Csession>\u002F` in the project, under `logging_dir` when\nthe settings name one). The crash section starts with `clice \u003Cversion>\n\u003Ctarget>` and the link to the commit's source —\ndownload that release's `*.symbols.tar.xz` (`.zip` for Windows; GSYM) and run:\n\n```bash\npython scripts\u002Fsymbolize.py crash.log --symbols clice.gsym\n```\n\nEvery CI platform that packages runs this path on its own package: the package's clice\ncrashes on purpose and its trace symbolizes against the symbol package\n(`scripts\u002Fcheck_crash_symbols.py`).\n\nFor core-dump-level debugging, fetch the full DWARF from the `debug-info-*`\nartifact of the main CI run that built the release (90-day retention; find\nit via the commit hash in the release notes). If the log predates the\nversion line or the release was pruned, symbolization is not possible — ask\nthe user to reproduce on a current nightly.\n",{"name":5,"description":7},"main","4e1e435a5ef755b61cfc0dd1312d9766781e555b",".claude\u002Fskills\u002Frelease",89,"https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice","https:\u002F\u002Fdocs.clice.io\u002Fclice\u002F","https:\u002F\u002Fgithub.com\u002Fclice-io","https:\u002F\u002Fclice.io\u002F","2026-11-15 03:05:59",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add clice-io\u002Fclice --skill release",{"tool":48,"command":49},"bunx","bunx skills add clice-io\u002Fclice --skill release",{"tool":51,"command":52},"pnpm","pnpm dlx skills add clice-io\u002Fclice --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frelease\u002FSKILL.md",true,[],[57,85,106,127,146,168],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":73,"publishedAt":28},"01M6BZFHCK196E4Z66DGN9QDYJ","write-tests","Read before writing or modifying anything under tests\u002F or unittests\u002F, or the tools' own tests — the case workflow, unit tests, hard rules and known pitfalls.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-tests\u002FSKILL.md",[63,68],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[74,75,76,77,22,78,79,80,81,82,83,84],"write tests","tests","write","pitfalls","case","unit","unit tests","Tools","workflow","Rules","writing",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":28},"01M6BZFEQ2NCYCKQX0RTMQM55A","upgrade-llvm","Read before upgrading xclang\u002FLLVM (arg = the xclang version, e.g. 23.1.2.1), touching MODULE.bazel, .bazelrc, BUILD.bazel or bazel\u002F, or regenerating modules\u002F — after a library bump, or when clice needs a header or macro it does not export.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fupgrade-llvm\u002FSKILL.md",[],[92,93,94,95,96,97,22,98,99,100,101,102,103,104,105],"upgrade llvm","llvm","upgrade","export","it","library","build","version","when","module","bump","modules","bazel","macro",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":28},"01M6BZFCM31QYASHF2XF6G105C","triage","Use when asked to triage issues — classifies untriaged issues with codex, validates the labels, and returns proposed labels plus an activity digest. Read-only; runs in a forked context.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftriage\u002FSKILL.md",[],[108,113,114,115,116,22,117,118,119,100,120,121,122,123,124,125,126],"fork","context","activity","triage issues","digest","returns","with","use","codex","only","labels","read-only","issues","activity digest",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":28},"01M6BZFAW6TTR0FK91HZ0TVNFS","translate-docs","Read before translating, reviewing or editing any docs\u002Fzh page — clice's glossary and page conventions, on top of the shared translation rules of clice-io\u002Fdocs.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftranslate-docs\u002FSKILL.md",[],[134,135,136,137,138,139,22,140,141,142,143,144,83,145],"docs","translate","translate docs","conventions","io","zh","top","translation","shared","editing","page","glossary",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":28},"01M6BZF86F54V9BZCW3MJW82VY","test","Run the clice test suites, on a box unless a local run is truly necessary; also how to test on Windows. Optional args = suite (unit | cases | all, default all) build type (Debug | RelWithDebInfo, default RelWithDebInfo) and the box id the build ran on. Runs in a forked context; only a digest returns.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftest\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000008","测试与质量",[148,156,79,118,157,158,159,160,161,162,163,114,164,117,98,113,165,166,122,167],"default","run","how","debug","box","windows","local","local run","suite","id","type","how to",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":28},"01M6BZF5WRJ6PKYJVW4YKPYD20","resolve-comments","Use in each watch round of an open PR — pulls its unresolved review threads, fixes them in the worktree, resolves them, and returns a compact summary.","https:\u002F\u002Fgithub.com\u002Fclice-io\u002Fclice\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fresolve-comments\u002FSKILL.md",[],[175,176,120,177,178,179,180,181,118,182,183,184,185,186],"comments","resolve comments","watch","compact","summary","fixes","threads","review","open pr","worktree","pr","open"]