@namewta/speculo 1.0.18 → 1.0.20

package/template/skills/github-npm-ops/references/version-bump-flow.md

@@ -1,217 +0,0 @@
-# 版本 bump → release commit → tag → push 端到端 SOP
-
-把"想发个新版本"翻译成可复现的几条命令。本文档假设仓库已有 `release.yml`(`v*` tag 触发,含 release-notes 注入)。
-
-## 0. 前置检查
-
-```bash
-# 1. main 干净,没有未提交改动
-git status
-
-# 2. 当前 HEAD 与 origin/main 的关系
-git log origin/main..HEAD --oneline
-
-# 3. 上一次发布的 tag
-git tag --sort=-version:refname | head -3
-
-# 4. CHANGELOG 顶部 [Unreleased] 段落已写好本次内容
-head -30 CHANGELOG.md
-```
-
-任意一项异常先解决再发版：工作区不干净 → 先提交，或调用 docs-sync 按其清洁契约处理；`[Unreleased]` 为空 → 先做 docs-sync。禁止用 stash 隐藏待发布改动。
-
-## 1. 维护 CHANGELOG
-
-`CHANGELOG.md` 顶部必须始终保留 `[Unreleased]` 段落。新版本发布时:
-
-1. 把 `[Unreleased]` 内容**整段迁移**到新建的 `## [X.Y.Z] — YYYY-MM-DD` 标题下
-2. 重新插入空的 `[Unreleased]` 段落
-3. 在文件末尾的"版本链接"段更新 compare 链接
-
-```diff
- ## [Unreleased]
-+
-+---
-+
-+## [0.0.10] — 2026-05-17
-
- ### Changed
- - ...
-```
-
-```diff
--- [Unreleased](https://github.com/owner/repo/compare/v0.0.9...HEAD)
-+- [Unreleased](https://github.com/owner/repo/compare/v0.0.10...HEAD)
-+- [0.0.10](https://github.com/owner/repo/releases/tag/v0.0.10)
- - [0.0.9](https://github.com/owner/repo/releases/tag/v0.0.9)
-```
-
-完整 CHANGELOG 契约见 `<Path>{roots.skills}/docs-sync/references/changelog-contract.md</Path>`。
-
-## 2. bump package.json
-
-**用 `npm version` 还是手改?**
-
-| 场景 | 推荐 |
-|------|------|
-| 单一 package.json,简单 bump | `npm version <major\|minor\|patch> --no-git-tag-version` |
-| Monorepo / 多文件版本号要同步 | 手改 + `pnpm -r`(或脚本) |
-| 已写好 CHANGELOG,只想改 package.json 一处 | 手改 |
-
-`--no-git-tag-version` 的关键作用:**只改文件,不自动打 tag**。我们要把 tag 打在 release commit 上,不是在 bump 这一刻。
-
-```bash
-# 等价于手改 package.json 的 version 字段
-npm version 0.0.10 --no-git-tag-version
-```
-
-## 3. release commit(原子提交)
-
-把 `package.json` + `CHANGELOG.md` 一并提交,使用 Conventional Commits 的 `chore(release):` 前缀。
-
-```bash
-git add package.json CHANGELOG.md
-git commit -m "chore(release): v0.0.10" \
-           -m "迁移 [Unreleased] 段落到 0.0.10:<一两句关键变更摘要>"
-```
-
-**为什么必须是同一个 commit**:
-- tag 要精确指向这个 commit
-- workflow 的 `Verify tag matches package version` 步骤会校验该 commit 上的 `package.json` 版本与 tag 一致
-- 利于后续 `git revert` 一键回滚发布
-
-## 4. push main
-
-```bash
-git push origin main
-```
-
-push **必须先于** tag,否则远端 tag 会指向 origin 看不到的 commit,GitHub Release 创建时会找不到对应 commit 树。
-
-## 5. 打 tag 并精确指向 release commit
-
-```bash
-# 显式指定 commit SHA,避免 HEAD 已经向前移动
-RELEASE_COMMIT=$(git log -1 --format=%H --grep="^chore(release): v0.0.10")
-
-git tag v0.0.10 "$RELEASE_COMMIT"
-git push origin v0.0.10
-```
-
-**为什么要指定 SHA 而不是直接 `git tag v0.0.10`**:
-
-如果 release commit 之后又做了几笔 docs / state 推进 commit,`HEAD` 不再是 release commit。直接 `git tag` 会把 tag 打在 docs commit 上,导致:
-
-- `Verify tag matches package version` 仍然通过(版本号对得上)
-- 但 `gh release view --json targetCommitish` 指向 docs commit
-- 长远看 release tag 与"真正的发布动作"脱钩
-
-简单场景下(release commit 就是 HEAD)直接 `git tag v0.0.10` 也对,但养成显式 SHA 的习惯更稳。
-
-## 6. 监控 workflow
-
-```bash
-# 实时跟踪
-gh run watch
-
-# 或周期性查询
-gh run list --workflow release.yml --limit 3 \
-  --json databaseId,status,conclusion,displayTitle,headBranch
-```
-
-预期顺序(11 步,缺一不可):
-
-1. Set up job
-2. Checkout
-3. Setup environment
-4. **Verify tag matches package version**
-5. Run lint
-6. Run tests
-7. Build
-8. **Verify bin entry**
-9. **Extract release notes from CHANGELOG.md** ← v1.1.0 新增
-10. **Publish to npm**
-11. **Create GitHub Release**
-
-## 7. 三端验证
-
-完整命令与判定见 [release-pipeline.md](release-pipeline.md) Phase 5（`npm view` / `gh release view` / `gh run view`）。任一缺失视为发布残次品；Release 正文为空时按 [release-notes-injection.md](release-notes-injection.md) 事后修复。
-
-## 8. 失败回滚
-
-### 8.1 publish 前任意步骤失败
-
-最干净:删 tag 重打。
-
-```bash
-git tag -d v0.0.10
-git push origin :refs/tags/v0.0.10
-
-# 修问题 → 重新 commit(若 release commit 也要改,用 amend)
-git commit --amend
-git push origin main --force-with-lease    # 仅当 amend 了已 push 的 commit 时
-
-# 重新打
-git tag v0.0.10 <commit-sha>
-git push origin v0.0.10
-```
-
-### 8.2 publish 已成功但后续步骤失败
-
-npm 已上线 → **不要**改版本号,只补后续动作。
-
-下面的 `notes_file` 只是一次性传给 `gh --notes-file` 的中间文件；若需要保留发布摘要或 release notes，由调用方写入 `<Path>{roots.state}/commands/{command}/{date}-{scope}-{topic}[-NN].md</Path>`。
-
-```bash
-notes_file="$(mktemp -t speculo-release-notes.XXXXXX)"
-trap 'rm -f "$notes_file"' EXIT
-
-# 抽取 CHANGELOG 段落
-awk -v v="0.0.10" '...' CHANGELOG.md > "$notes_file"
-
-# 手动创建 GitHub Release
-gh release create v0.0.10 --notes-file "$notes_file" --latest
-
-# 或编辑已有 Release(如果 action 半成品创建过空 Release)
-gh release edit v0.0.10 --notes-file "$notes_file"
-```
-
-### 8.3 publish 失败但 npm 上其实有了(罕见)
-
-```bash
-# 确认状态
-npm view @scope/pkg@0.0.10 version
-
-# 如果有,说明上传完但 npm 返回失败码,直接当作 8.2 处理(已发,只补 Release)
-# 如果无,按 8.1 处理(重打 tag)
-```
-
-### 8.4 npm 不允许重发同一 version
-
-铁律:即使 `npm unpublish` 过,**24h 内同一版本号也不能再发**。若 publish 真上传成功但需要修代码:
-
-```bash
-# bump 到下一个补丁
-npm version 0.0.11 --no-git-tag-version
-git add package.json CHANGELOG.md
-git commit -m "chore(release): v0.0.11"
-git push origin main
-git tag v0.0.11
-git push origin v0.0.11
-```
-
-## 9. CHECKLIST
-
-发版前过一遍:
-
-- [ ] `git status` 干净
-- [ ] CHANGELOG 顶部已迁移 `[Unreleased]` 到新版本段
-- [ ] 底部 compare 链接已更新
-- [ ] `package.json` version 与即将打的 tag 严格一致(去掉 `v` 前缀)
-- [ ] `pnpm check` 本地通过(lint + test + build)
-- [ ] `pnpm build:check-bin` 通过(若是 CLI 包)
-- [ ] release commit 已 push 到 origin/main
-- [ ] tag 指向 release commit(不是 docs commit / HEAD 漂移后的 commit)
-- [ ] tag 已 push,`gh run list` 看到 workflow 触发
-- [ ] workflow 11 步全 success
-- [ ] 三端验证齐全:npm 有 / Release body 非空 / workflow success

package/template/skills/github-npm-ops/references/workflow-yaml-reference.md

@@ -1,268 +0,0 @@
-# release.yml 完整注解
-
-逐行解释 `.github/workflows/release.yml` 中每个选择的原因。
-
-## 完整示例
-
-```yaml
-name: Release
-
-on:
-  push:
-    tags:
-      - 'v*'
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    name: Release to npm
-    permissions:
-      id-token: write
-      contents: write
-      packages: write
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup environment
-        uses: ./.github/actions/setup
-        with:
-          registry-url: 'https://registry.npmjs.org'
-
-      - name: Verify tag matches package version
-        run: |
-          TAG="${{ github.ref }}"
-          TAG_VERSION="${TAG#refs/tags/v}"
-          PACKAGE_VERSION=$(node -e "console.log(require('./package.json').version)")
-          if [ "$TAG_VERSION" != "$PACKAGE_VERSION" ]; then
-            echo "Tag version ($TAG_VERSION) does not match package.json version ($PACKAGE_VERSION)"
-            exit 1
-          fi
-          echo "Version verified: v$PACKAGE_VERSION"
-
-      - name: Run lint
-        run: pnpm lint
-
-      - name: Run tests
-        run: pnpm test
-
-      - name: Build
-        run: pnpm build
-
-      - name: Verify bin entry
-        run: node scripts/verify-bin.mjs
-
-      - name: Extract release notes from CHANGELOG.md
-        run: |
-          VERSION="${GITHUB_REF_NAME#v}"
-          awk -v v="$VERSION" '
-            $0 ~ "^## \\["v"\\]" { found=1; print; next }
-            found && /^## \[/ { exit }
-            found && /^---[[:space:]]*$/ { next }
-            found { print }
-          ' CHANGELOG.md > release-notes.md
-
-          if [ ! -s release-notes.md ]; then
-            echo "::warning::CHANGELOG.md 中未找到 [$VERSION] 段落，回退到自动生成。"
-            echo "See [CHANGELOG.md](https://github.com/${{ github.repository }}/blob/main/CHANGELOG.md) for details." > release-notes.md
-          fi
-
-      - name: Publish to npm
-        run: npm publish --provenance --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-      - name: Create GitHub Release
-        uses: softprops/action-gh-release@v2
-        if: success()
-        with:
-          tag_name: ${{ github.ref_name }}
-          name: Release ${{ github.ref_name }}
-          body_path: release-notes.md
-          generate_release_notes: true
-          draft: false
-          prerelease: false
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-
-## 逐项解释
-
-### 触发条件
-
-```yaml
-on:
-  push:
-    tags:
-      - 'v*'
-```
-
-- 只在 push 带 `v` 开头的 tag 时触发（如 `v0.0.2`、`v1.2.3-rc1`）
-- **不要**同时写 `branches`，否则每次 push main 都会触发 release
-- 如果想预发，用独立的 tag 模式（如 `v*-rc*`）区分
-
-### permissions
-
-```yaml
-permissions:
-  id-token: write
-  contents: write
-  packages: write
-```
-
-| 权限               | 作用                                                                                   |
-| ------------------ | -------------------------------------------------------------------------------------- |
-| `id-token: write`  | **必需**：用于 npm provenance（OIDC 签名）                                              |
-| `contents: write`  | **必需**：`softprops/action-gh-release` 创建 GitHub Release 需要                        |
-| `packages: write`  | 仅在同时发 GitHub Packages 时需要；纯 npm 发布可省略                                    |
-
-默认 `GITHUB_TOKEN` 只有 `contents: read`，这三项必须显式声明。
-
-### Checkout
-
-```yaml
-- uses: actions/checkout@v4
-```
-
-默认浅克隆（`fetch-depth: 1`）。如果发布说明需要完整历史（如 changelog 生成），加 `fetch-depth: 0`。
-
-### Setup environment
-
-```yaml
-- uses: ./.github/actions/setup
-  with:
-    registry-url: 'https://registry.npmjs.org'
-```
-
-复合 action，通常封装：
-
-```yaml
-- uses: actions/setup-node@v4
-  with:
-    node-version: '24.14.1'
-    registry-url: 'https://registry.npmjs.org'
-- uses: pnpm/action-setup@v2
-  with:
-    version: 9
-- run: pnpm install --frozen-lockfile
-```
-
-关键点：`registry-url` **必须**在 `setup-node` 里设置，它会生成 `.npmrc` 并让 `NODE_AUTH_TOKEN` 生效。
-
-### Verify tag matches package version
-
-防止错发：tag `v0.0.2` 指向一个 `package.json` 版本为 `0.0.1` 的 commit，会导致用户安装到错误版本。
-
-失败时 workflow 直接退出，不会执行任何发布动作。
-
-### Lint / Test / Build
-
-即使本地已经跑过，CI 再跑一遍保证：
-
-1. 发布的产物来自干净环境
-2. 锁文件（`pnpm-lock.yaml`）在 CI 下可复现
-3. Build 产物与 tag 对应的源码一致
-
-如果 repo 已有一个单独的 `ci.yml` 跑在 push/PR 上，这里仍保留是为了**再次校验 tag 指向的 commit**——tag 可能指向旧 commit。
-
-### Verify bin entry
-
-```yaml
-- run: node scripts/verify-bin.mjs
-```
-
-CLI 包专有：确认 `dist/cli/index.js` 存在、有 shebang、可执行。防止 tsconfig 出问题导致产物不完整。
-
-### Extract release notes from CHANGELOG.md
-
-```yaml
-- name: Extract release notes from CHANGELOG.md
-  run: |
-    VERSION="${GITHUB_REF_NAME#v}"
-    awk -v v="$VERSION" '
-      $0 ~ "^## \\["v"\\]" { found=1; print; next }
-      found && /^## \[/ { exit }
-      found && /^---[[:space:]]*$/ { next }
-      found { print }
-    ' CHANGELOG.md > release-notes.md
-
-    if [ ! -s release-notes.md ]; then
-      echo "::warning::..." >&2
-      echo "See [CHANGELOG.md](...) for details." > release-notes.md
-    fi
-```
-
-把 `## [X.Y.Z]` 段落抽到 `release-notes.md`，让下面的 `softprops/action-gh-release` 通过 `body_path` 注入到 GitHub Release 正文。
-
-**为什么必须有这一步**：仅用 `generate_release_notes: true` 时，GitHub 内部从 commit + PR + label 抽取 changelog；直 push main 流程没 PR，生成器只剩 `Full Changelog: vA...vB` 一行。CHANGELOG 是事实来源，注入它才能让 Release 正文非空。
-
-**awk 规则细节**与边界用例（包含 `[Unreleased]` 同时存在、版本号含连字符 / 多语言 CHANGELOG / `body_path` + `generate_release_notes` 共存语义）见 [release-notes-injection.md](release-notes-injection.md)。
-
-### Publish to npm
-
-```yaml
-- run: npm publish --provenance --access public
-  env:
-    NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-```
-
-- `--provenance`：生成 sigstore 签名，要求 `id-token: write`
-- `--access public`：scoped 包首次发布必需；非 scoped 包加了也不会错
-- **位置在 GitHub Release 之前**：npm publish 不可回滚，如果后续步骤失败，至少 npm 发布是成功的
-
-### Create GitHub Release
-
-```yaml
-- uses: softprops/action-gh-release@v2
-  if: success()
-  with:
-    tag_name: ${{ github.ref_name }}
-    body_path: release-notes.md
-    generate_release_notes: true
-```
-
-- `if: success()`：只在 npm publish 成功后执行
-- `body_path: release-notes.md`：**正文头部**注入上一步抽取的 CHANGELOG 段落
-- `generate_release_notes: true`：**正文尾部**附 GitHub 自动生成的 What's Changed + Full Changelog compare 链接
-- 两者共存不冲突，效果是「人写的精炼说明 + 机器可追溯的索引」叠加
-- `softprops/action-gh-release@v2` 比废弃的 `actions/create-release@v1` 更稳定
-
-仅用 `generate_release_notes: true` 而不注入 `body_path`，在没有 PR 流量的仓库会得到几乎为空的 Release 正文，详见 [release-notes-injection.md](release-notes-injection.md) §1。
-
-## 常见变体
-
-### 使用 pnpm publish 代替 npm publish
-
-pnpm 也支持 `--access public --provenance`：
-
-```yaml
-- run: pnpm publish --provenance --access public --no-git-checks
-```
-
-`--no-git-checks` 避免 pnpm 检查当前 branch/tag（CI 中 detached HEAD 会被拒）。
-
-### 发布到 GitHub Packages（可选）
-
-```yaml
-- name: Publish to GitHub Packages
-  run: npm publish --registry=https://npm.pkg.github.com
-  env:
-    NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-```
-
-需要单独的 setup step 指向 GitHub Packages，且 package 名必须是 `@owner/name` 形式。
-
-### Dry run（在 PR 里预演）
-
-```yaml
-- run: npm publish --dry-run --access public
-```
-
-放在一个仅 PR 触发的 workflow 里，帮你在合并前发现 tarball 问题。
-
-## 不推荐的做法
-
-- 在同一个 job 里既跑 push-to-main CI 又跑 release — 混乱，难以调试
-- 使用 `actions/create-release@v1` — 已废弃，推荐 `softprops/action-gh-release`
-- 用 `secrets.NPM_TOKEN` 直接传给 `npm publish` 命令行 — 会在日志里泄露
-- 跳过 `prepublishOnly` 或 CI 测试 — 已知会发布过坏包

package/template/skills/github-npm-ops/scripts/issue-transport.mjs

@@ -1,227 +0,0 @@
-#!/usr/bin/env node
-
-import { execFile } from "node:child_process";
-import { readFile } from "node:fs/promises";
-import { promisify } from "node:util";
-
-const execFileAsync = promisify(execFile);
-
-function parseArgs(argv) {
-  const [operation, ...rest] = argv;
-  const options = { labels: [] };
-  for (let index = 0; index < rest.length; index += 1) {
-    const token = rest[index];
-    if (token === "--apply") {
-      options.apply = true;
-      continue;
-    }
-    if (!token.startsWith("--")) throw new Error(`unexpected argument: ${token}`);
-    const key = token.slice(2).replaceAll("-", "_");
-    const value = rest[index + 1];
-    if (value === undefined || value.startsWith("--")) {
-      throw new Error(`${token} requires a value`);
-    }
-    index += 1;
-    if (key === "label") options.labels.push(value);
-    else options[key] = value;
-  }
-  return { operation, options };
-}
-
-function requireOptions(options, keys) {
-  const missing = keys.filter((key) => !String(options[key] ?? "").trim());
-  if (missing.length) throw new Error(`missing options: ${missing.map((key) => `--${key.replaceAll("_", "-")}`).join(", ")}`);
-}
-
-async function gh(args) {
-  try {
-    const { stdout } = await execFileAsync("gh", args, {
-      maxBuffer: 16 * 1024 * 1024,
-      encoding: "utf8",
-    });
-    return stdout.trim();
-  } catch (error) {
-    const detail = String(error?.stderr || error?.message || error).trim();
-    throw new Error(`gh ${args[0]} failed: ${detail}`);
-  }
-}
-
-async function readIssue(repo, number) {
-  return JSON.parse(
-    await gh([
-      "issue",
-      "view",
-      number,
-      "--repo",
-      repo,
-      "--json",
-      "number,title,body,state,url,author,labels,createdAt,updatedAt,comments",
-    ]),
-  );
-}
-
-async function issueRead(options) {
-  requireOptions(options, ["repo", "number"]);
-  const issue = await readIssue(options.repo, options.number);
-  return {
-    operation: "issue-read",
-    provider: "github",
-    repo: options.repo,
-    kind: "issue",
-    ...issue,
-  };
-}
-
-async function prRead(options) {
-  requireOptions(options, ["repo", "number"]);
-  const pull = JSON.parse(
-    await gh([
-      "pr",
-      "view",
-      options.number,
-      "--repo",
-      options.repo,
-      "--json",
-      "number,title,body,state,url,author,labels,createdAt,updatedAt,comments,baseRefName,baseRefOid,headRefName,headRefOid,files",
-    ]),
-  );
-  return {
-    operation: "pr-read",
-    provider: "github",
-    repo: options.repo,
-    kind: "pull-request",
-    ...pull,
-  };
-}
-
-async function issueSearch(options) {
-  requireOptions(options, ["repo", "query"]);
-  const issues = JSON.parse(
-    await gh([
-      "issue",
-      "list",
-      "--repo",
-      options.repo,
-      "--search",
-      options.query,
-      "--state",
-      options.state || "all",
-      "--limit",
-      options.limit || "20",
-      "--json",
-      "number,title,state,url,labels,updatedAt",
-    ]),
-  );
-  return { operation: "issue-search", provider: "github", repo: options.repo, issues };
-}
-
-async function issueCreate(options) {
-  requireOptions(options, ["repo", "title", "body_file"]);
-  const plan = {
-    operation: "issue-create",
-    provider: "github",
-    repo: options.repo,
-    title: options.title,
-    body_file: options.body_file,
-    labels: options.labels,
-    mode: options.apply ? "apply" : "dry-run",
-  };
-  if (!options.apply) return plan;
-
-  await readFile(options.body_file, "utf8");
-  const args = [
-    "issue",
-    "create",
-    "--repo",
-    options.repo,
-    "--title",
-    options.title,
-    "--body-file",
-    options.body_file,
-  ];
-  for (const label of options.labels) args.push("--label", label);
-  return { ...plan, url: await gh(args), status: "created" };
-}
-
-async function issueCommentClose(options) {
-  requireOptions(options, ["repo", "number", "comment_file", "marker"]);
-  const marker = `<!-- ${options.marker} -->`;
-  const comment = (await readFile(options.comment_file, "utf8")).trim();
-  const before = await readIssue(options.repo, options.number);
-  const markerExists = (before.comments ?? []).some((item) =>
-    String(item?.body ?? "").includes(marker),
-  );
-  const plan = {
-    operation: "issue-comment-close",
-    provider: "github",
-    repo: options.repo,
-    number: Number(options.number),
-    url: before.url,
-    mode: options.apply ? "apply" : "dry-run",
-    state_before: before.state,
-    comment_required: !markerExists,
-    close_required: String(before.state).toUpperCase() !== "CLOSED",
-    marker: options.marker,
-    steps: [],
-  };
-  if (!options.apply) return plan;
-
-  if (!markerExists) {
-    await gh([
-      "issue",
-      "comment",
-      options.number,
-      "--repo",
-      options.repo,
-      "--body",
-      `${comment}\n\n${marker}`,
-    ]);
-    plan.steps.push("commented");
-  } else {
-    plan.steps.push("comment-already-present");
-  }
-  if (String(before.state).toUpperCase() !== "CLOSED") {
-    await gh([
-      "issue",
-      "close",
-      options.number,
-      "--repo",
-      options.repo,
-      "--reason",
-      options.reason || "completed",
-    ]);
-    plan.steps.push("closed");
-  } else {
-    plan.steps.push("already-closed");
-  }
-
-  const after = await readIssue(options.repo, options.number);
-  if (String(after.state).toUpperCase() !== "CLOSED") {
-    throw new Error(`issue remained ${after.state} after close operation`);
-  }
-  return { ...plan, state_after: after.state, status: "closed" };
-}
-
-function usage() {
-  return `Usage:
-  issue-transport.mjs issue-read --repo OWNER/REPO --number N
-  issue-transport.mjs pr-read --repo OWNER/REPO --number N
-  issue-transport.mjs issue-search --repo OWNER/REPO --query TEXT [--state all] [--limit 20]
-  issue-transport.mjs issue-create --repo OWNER/REPO --title TEXT --body-file PATH [--label LABEL] [--apply]
-  issue-transport.mjs issue-comment-close --repo OWNER/REPO --number N --comment-file PATH --marker ID [--reason completed] [--apply]`;
-}
-
-try {
-  const { operation, options } = parseArgs(process.argv.slice(2));
-  if (!operation || ["help", "--help", "-h"].includes(operation)) {
-    console.log(usage());
-  } else {
-    const handlers = { issueRead, prRead, issueSearch, issueCreate, issueCommentClose };
-    const handler = handlers[operation.replace(/-([a-z])/g, (_, letter) => letter.toUpperCase())];
-    if (!handler) throw new Error(`unknown operation: ${operation}\n${usage()}`);
-    console.log(JSON.stringify(await handler(options), null, 2));
-  }
-} catch (error) {
-  console.error(`ERROR: ${error.message}`);
-  process.exitCode = 1;
-}