Skip to content

chore(governance): add PR fork base rails (LL-080) #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bouillipx wants to merge 9 commits into
base: develop
Choose a base branch
from
Open

chore(governance): add PR fork base rails (LL-080) #37

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
8406e11
chore(governance): add PR fork base rails (LL-080)
bouillipx Jun 28, 2026
9edc193
fix(#37): address 砚砚 P2/P3 + cloud P1 — exact match + ${GH_REPO} + fu…
bouillipx Jun 28, 2026
7e25f8e
fix(#37): drop hardcoded cat name in SKILL.md per check-skills-manife…
bouillipx Jun 28, 2026
e666221
fix(#37): pin --repo on Quick Reference + Common Mistakes shortcuts (…
bouillipx Jun 28, 2026
1e1a240
fix(#37): rename .envrc → .envrc.example per Config Immutability (clo…
bouillipx Jun 28, 2026
9729bd0
fix(#37): document GH_REPO leak risk on manual source (cloud R4 P2)
bouillipx Jun 28, 2026
341dd7f
fix(#37): split .gitignore inline comment to enable .envrc rule (clou…
bouillipx Jun 28, 2026
929fd13
chore(#37): renumber LL-080 → LL-090 to resolve collision with main
bouillipx Jul 8, 2026
195cc48
fix(#37): pin --repo on E1 validation table + post-merge note (cloud …
bouillipx Jul 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions .claude/hooks/user-level/session-start-recall.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,29 @@ ${ROOT_CLUTTER}
"
fi

# 7. Fork base trap 检测（LL-090）
# user-level hook：跨项目共享，必须**精确**匹配仓 slug，不能 substring。
# 砚砚 P2 (PR #37): substring `*clowder-labs/clowder-ai*` 会误伤 `clowder-labs/clowder-ai-docs` 等前缀仓。
# 修法：normalize origin URL → owner/repo 形式（支持 https/ssh + 可选 .git 后缀），再 == 精确比较。
ORIGIN_URL=$(git config --get remote.origin.url 2>/dev/null)
REPO_SLUG=$(echo "$ORIGIN_URL" | sed -E 's#^.+[/:]([^/:]+/[^/:]+)$#\1#; s#\.git$##')
if [ "$REPO_SLUG" = "clowder-labs/clowder-ai" ]; then
# 检测 GH_REPO 兜底是否生效
# 砚砚 P3 (PR #37): `$GH_REPO` 紧贴全角中文括号在 bash locale 下解析坏，错误值被吞成 ��。用 ${GH_REPO} 显式包裹。
if [ "${GH_REPO}" = "clowder-labs/clowder-ai" ]; then
GH_REPO_STATUS="GH_REPO 兜底已生效"
elif [ -z "${GH_REPO}" ]; then
GH_REPO_STATUS="GH_REPO 未设——\`cp .envrc.example .envrc && direnv allow\`（推荐）或 per-command \`GH_REPO=clowder-labs/clowder-ai gh ...\`（无 direnv 时不污染 session）"
else
GH_REPO_STATUS="⚠️ GH_REPO=${GH_REPO} (不是 clowder-labs/clowder-ai，可能误导 gh CLI)"
fi
WARNINGS="${WARNINGS}
⚠️ 本仓在 GitHub 是 zts212653/clowder-ai 的 fork（LL-090）
→ \`gh pr create\` 必须显式 \`--repo clowder-labs/clowder-ai --base main\`，否则默认提到 parent (zts212653)
→ ${GH_REPO_STATUS}
"
fi

# 输出提醒（只在有警告时才输出）
if [ -n "$WARNINGS" ]; then
echo "🐾 开工自检：${WARNINGS}"
Expand Down
43 changes: 43 additions & 0 deletions .envrc.example
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# ============================================================
# Cat Cafe / Clowder AI — Shell environment 模板（手敲命令时兜底）
# ============================================================
#
# 这个文件是**模板**（.envrc.example），不直接生效。
# 用户主动 `cp .envrc.example .envrc` 后才会被 direnv 自动 source。
#
# 设计选择（AGENTS.md / CLAUDE.md Config Immutability 铁律）：
# runtime shell 配置不通过 commit 渗透。team-level 提供模板，individual 自己启用。
# 这样审查/回滚 GH_REPO 改动归个人 git 操作，不进 PR review 影子层。
#
# 这个文件的作用：补 §SOP 之外的"手敲命令"场景。
# 详见 LL-090（PR Fork Base Trap）+ cat-cafe-skills/merge-gate/SKILL.md。
#
# 启用步骤（按你的环境三选一，优先级从上到下）：
# 1. direnv（**强推荐** — 进出 repo 自动 export/unset，无 cross-repo 污染）：
# brew install direnv
# # shell rc 加：eval "$(direnv hook zsh)"
# cp .envrc.example .envrc
# direnv allow # 进入本仓自动 export，离开自动 unset
#
# 2. Per-command 前置（无 direnv 时**推荐替代**，不污染 session）：
# GH_REPO=clowder-labs/clowder-ai gh pr view {N}
# GH_REPO=clowder-labs/clowder-ai gh issue create ...
#
# 3. 手动 source（**有副作用**，仅限短任务且离开本仓前必须清理）：
# ⚠️ PR #37 cloud R4 P2：`source .envrc.example` 会把 GH_REPO **持久 export**
# 到整个 shell session。之后 cd 到其他 repo，`gh pr/issue` 仍被强制路由到
# clowder-labs/clowder-ai——这正是这条 rail 防的**同类错路由**（GH_REPO
# 反向污染 vs fork base 默认路由，同一类错仓 mutation）。
# 用法（自带清理）：
# source .envrc.example
# gh pr ... # 你的工作
# unset GH_REPO # ❗ 离开本 repo / 换任务前必清理
#
# 注：cat-cafe-skills 里的 SOP 命令已经显式 `--repo clowder-labs/clowder-ai`，
# 不依赖 GH_REPO；这里是给"绕开 SOP、直接敲 gh 命令"的猫兜底用。
# ============================================================

# Fork base trap 兜底：本仓在 GitHub 是 zts212653/clowder-ai 的 fork，
# 不显式 --repo / GH_REPO 时，gh CLI 会默认把 PR / issue 提到 parent。
# 历史事故：PR #1030 (2026-06-26) 误提到 zts，10 分钟后 close + 重建 PR #30。
export GH_REPO="clowder-labs/clowder-ai"
3 changes: 3 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,9 @@ packages/web/public/vendor/
.env
.env.local
.env.*.local
# LL-080 Config Immutability: only .envrc.example is committed
# cloud R5 P2: gitignore 不支持行尾内联注释——必须独占一行才会被解析为 pattern
.envrc

# Local overlay files (#603 .local convention, F225 prompt templates)
*.local.md
Expand Down
50 changes: 30 additions & 20 deletions cat-cafe-skills/merge-gate/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ triggers:
进入 Step 7 之前，author 必须核对：

```bash
CURRENT_HEAD="$(gh pr view {PR_NUMBER} --json headRefOid --jq '.headRefOid')"
CURRENT_HEAD="$(gh pr view {PR_NUMBER} --repo clowder-labs/clowder-ai --json headRefOid --jq '.headRefOid')"
echo "$CURRENT_HEAD"
```

Expand Down Expand Up @@ -114,7 +114,7 @@ merge-gate 执行时，在 Step 7（squash merge）**之前**，猫必须**组

| # | 检查项 | 验证方式 | 失败动作 |
|---|--------|----------|----------|
| E1 | `head` === PR current HEAD | `git rev-parse HEAD` vs `gh pr view {PR_NUMBER} --json headRefOid --jq '.headRefOid'` | BLOCKED — HEAD 不一致，可能有 unpushed commit |
| E1 | `head` === PR current HEAD | `git rev-parse HEAD` vs `gh pr view {PR_NUMBER} --repo clowder-labs/clowder-ai --json headRefOid --jq '.headRefOid'` | BLOCKED — HEAD 不一致，可能有 unpushed commit |
| E2 | `stale` === false | 按 `headChangeCause` 判定的活跃 review 源覆盖当前 `head`（见上方 `stale` 字段定义的完整映射表）。`nextGateOwner=author` 时（merge-ready 态），沿用最后一次 `headChangeCause` 确定的活跃源；`nextGateOwner=ci/guardian` 时，review 覆盖规则不变（CI/guardian 是额外 gate，不改变 review 覆盖链） | BLOCKED — 活跃 review 源的 SHA 过期，需要 re-review |
| E3 | reviewer provenance 闭合 | 至少一个 review 源（local 或 cloud）非空且覆盖 `head`（exempt PR 无 cloud 时只看 local） | BLOCKED — 缺 review provenance |
| E4 | `verdict` !== "blocked" | review 结果为 APPROVE（非 BLOCK / CHANGES_REQUESTED） | BLOCKED — reviewer 未放行 |
Expand Down Expand Up @@ -193,12 +193,22 @@ fi

### 合入方式（唯一正确做法）

> **⚠️ Fork base trap 总规则（LL-090，覆盖本节所有命令）**：
> 本仓 `clowder-labs/clowder-ai` 在 GitHub 后台是 `zts212653/clowder-ai` 的 fork。
> **所有** `gh pr *` 和 `gh api repos/...` 命令在 fresh clone / 未写 `gh-resolved` 的
> worktree 上若不显式带 `--repo clowder-labs/clowder-ai`，gh CLI 会默认解析到 parent
> (zts212653) ——PR 创建、`gh pr view {N}`、`gh pr comment {N}`、`gh pr merge {N}`
> 全部会找错仓。**本节所有命令必须保持 `--repo clowder-labs/clowder-ai`**，并且新加命令时同步带上。
Comment on lines +198 to +201

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pin the remaining PR checks shortcut

In the fresh-clone / unresolved gh config context this new rule is meant to guard, the same file still leaves Quick Reference's cloud-pass check as gh pr checks {PR} without --repo, so following that shortcut can still query the fork parent even though this block now claims all PR-number commands are pinned. The GitHub CLI manual for gh pr checks documents the inherited -R, --repo <[HOST/]OWNER/REPO> selector (https://cli.github.com/manual/gh_pr_checks), so the quick reference should be updated to match the guarded command above.

Useful? React with 👍 / 👎.

Comment on lines +198 to +201

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pin the remaining gh examples

This new guardrail says every gh pr * command in the merge flow must be repo-pinned, but there are still unpinned examples in this same file: the E1 Evidence Validation table uses gh pr view {PR_NUMBER} --json headRefOid ..., and the post-merge note says gh pr merge --squash --delete-branch. In the fresh-clone/no-gh-resolved scenario described here, following either copyable snippet can still route to zts212653/clowder-ai, so the rail is incomplete.

Useful? React with 👍 / 👎.

> 历史事故：PR #1030 (2026-06-26) 误提到 zts，10 分钟后 close + 重建 PR #30。
> PR #37 cloud review P1：仅 pin `gh pr create` 不够，后续 PR-number 命令同样需要。

```bash
# 1. Push feature branch
git push origin {branch}

# 2. 开 PR（读 refs/pr-template.md 获取 body 模板，用 HEREDOC 填写）
gh pr create --title "feat(xxx): ..." --body "$(cat <<'EOF'
gh pr create --repo clowder-labs/clowder-ai --base main \

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Pin the repo on every PR command

This only pins gh pr create; in the fresh-clone/GH_REPO-unset case this rail is meant to cover, the rest of the same merge-gate still uses PR-number commands without --repo (gh pr view/comment/merge later in this file). The gh manual describes --repo as selecting another repository for the command, so after creating the PR in clowder-labs/clowder-ai, the body check, review trigger, and merge can still resolve against the fork parent by number unless .envrc happened to be loaded. Please carry --repo clowder-labs/clowder-ai through the subsequent PR commands or centralize it in a required variable.

Useful? React with 👍 / 👎.

--title "feat(xxx): ..." --body "$(cat <<'EOF'
... 按 refs/pr-template.md 模板填写 ...
EOF
)"
Expand All @@ -219,7 +229,7 @@ EOF
# ⚠️ 时机契约（fingerprint 去重边界）：在 CI **还没绿之前**翻成 merge 才保证被唤醒。
# CiCdRouter 按 headSha:bucket 去重——若同一 head 的 CI-pass 已在 review intent 下投递过，
# 之后再翻 merge **不会补发唤醒**。所以：若翻 intent 时 CI **已经绿了**，别等回调，直接
# `gh pr checks {PR}` 自查、继续 merge 流程（无新 head 时 CI 不会重跑、不会再有 pass 事件）。
# `gh pr checks {PR} --repo clowder-labs/clowder-ai` 自查、继续 merge 流程（无新 head 时 CI 不会重跑、不会再有 pass 事件）。
#
# 收到冲突通知时（F140 Phase B）：
# - 暂停当前工作，处理冲突优先（冲突是 merge blocker）
Expand All @@ -228,7 +238,7 @@ EOF
# - 复杂冲突 → 通知operator，等指示后再继续

# 4. PR body 防呆检查（禁止任何 @句柄出现在 body）
PR_BODY="$(gh pr view {PR_NUMBER} --json body --jq '.body')" || \
PR_BODY="$(gh pr view {PR_NUMBER} --repo clowder-labs/clowder-ai --json body --jq '.body')" || \
{ echo "❌ 无法读取 PR body，停止流程"; exit 1; }
printf '%s\n' "$PR_BODY" | rg -q '@[A-Za-z0-9_-]+ review' && \
{ echo "❌ 不合规：remote review 触发句柄只能写在 comment，不能写在 body"; exit 1; }
Expand All @@ -241,19 +251,19 @@ printf '%s\n' "$PR_BODY" | rg -q '@(codex|chatgpt-codex-connector|gpt52|opus|son
# 详见 refs/pr-template.md「云端 Review 触发 Comment 模板」

# 5.1 去重防呆
LAST_TRIGGER=”$(gh pr view {PR_NUMBER} --json comments | jq -r '
LAST_TRIGGER=”$(gh pr view {PR_NUMBER} --repo clowder-labs/clowder-ai --json comments | jq -r '
[.comments[] | select(.body | test(“^@codex\\s+review\\s*$”; “m”))] | last | .url // empty
')”
# 有已触发 → 检查是否需要重发（新 commit / create-environment 回复 / 无 👀）

gh pr comment {PR_NUMBER} --body '@codex review'
gh pr comment {PR_NUMBER} --repo clowder-labs/clowder-ai --body '@codex review'

# 6. 等remote review（事件驱动，不轮询）
#
# 6.1 👀 接单检测（触发后 5 分钟查一次）
TRIGGER_COMMENT_ID=”$(gh api repos/{OWNER}/{REPO}/issues/{PR_NUMBER}/comments \
TRIGGER_COMMENT_ID=”$(gh api repos/clowder-labs/clowder-ai/issues/{PR_NUMBER}/comments \
--jq '[.[] | select(.body | test(“^@codex\\s+review”; “m”))] | last | .id')”
EYES=”$(gh api repos/{OWNER}/{REPO}/issues/comments/${TRIGGER_COMMENT_ID}/reactions \
EYES=”$(gh api repos/clowder-labs/clowder-ai/issues/comments/${TRIGGER_COMMENT_ID}/reactions \
--jq '[.[] | select(.content == “eyes”)] | length')”
# - EYES > 0 → 云端已接单 → 停止监控，PR tracking 会自动通知结果。
# ⚠️ KD-27：此时必须释放 hold_ball，禁止续约轮询。PR tracking 回调是唯一通知渠道。
Expand Down Expand Up @@ -319,11 +329,11 @@ fi
IS_HOTFIX="$(echo "$HOTFIX_JSON" | jq -r '.hotfix // false')"
LABEL_ERROR="$(echo "$HOTFIX_JSON" | jq -r '.labelError // empty')"
if [ -n "$LABEL_ERROR" ]; then
echo "⚠️ Hotfix label 添加失败: $LABEL_ERROR — 请手动: gh pr edit {PR_NUMBER} --add-label hotfix"
echo "⚠️ Hotfix label 添加失败: $LABEL_ERROR — 请手动: gh pr edit {PR_NUMBER} --repo clowder-labs/clowder-ai --add-label hotfix"
fi
if [ "$IS_HOTFIX" = "true" ]; then
PR_AUTHOR="$(gh pr view {PR_NUMBER} --json author --jq '.author.login')"
REVIEWERS="$(gh pr view {PR_NUMBER} --json reviews --jq '[.reviews[] | select(.state == "APPROVED") | .author.login] | unique | join(",")')"
PR_AUTHOR="$(gh pr view {PR_NUMBER} --repo clowder-labs/clowder-ai --json author --jq '.author.login')"
REVIEWERS="$(gh pr view {PR_NUMBER} --repo clowder-labs/clowder-ai --json reviews --jq '[.reviews[] | select(.state == "APPROVED") | .author.login] | unique | join(",")')"
if [ -z "$REVIEWERS" ] || echo "$REVIEWERS" | grep -q "^${PR_AUTHOR}$"; then
echo "❌ Hotfix PR 必须有跨猫 review 放行（禁止 self-merge）"
echo " Author: $PR_AUTHOR | Approved by: ${REVIEWERS:-none}"
Expand All @@ -350,7 +360,7 @@ node scripts/check-feature-truth.mjs
# → 详见下方「Feature Doc Truth 核对（Step 7.5）」§ 7.5a（含人工核对项）

# 7. Squash merge（GitHub 处理，禁止本地 squash！）
gh pr merge {PR_NUMBER} --squash --delete-branch
gh pr merge {PR_NUMBER} --repo clowder-labs/clowder-ai --squash --delete-branch

# 7.5b Post-merge: 记录已合入状态（每次 merge 必做！）🔴
# Phase ✅ / AC 打勾 / Timeline 记 merged / Status 推进 → commit → 复跑 check-feature-truth
Expand Down Expand Up @@ -460,7 +470,7 @@ ReviewRouter 现在会在投递通知时**主动拉取** review body + inline co
merge 前仍需执行以下检查作为兜底：

```bash
gh api --paginate repos/{OWNER}/{REPO}/pulls/{PR_NUMBER}/comments \
gh api --paginate repos/clowder-labs/clowder-ai/pulls/{PR_NUMBER}/comments \
--jq '.[] | select(.body | test("\\bP[012]\\b"; "i")) | {body: .body[:200], path: .path}'
```

Expand Down Expand Up @@ -494,7 +504,7 @@ merge 是把状态写进 main 的不可逆点（其他 session 立即读到）

#### 7.5b — Post-merge：记录已合入状态（在 Step 7 merge 之后）

⚠️ **切到持有 main 的 worktree 再 commit**：`gh pr merge --squash --delete-branch` 之后你仍在 feature worktree 上。直接 commit 会落到**已合并/已删的 feature branch**（或留脏工作树让 Step 8 fail-closed abort）。而且 worktree 开发场景下 `main` 由主仓 worktree 持有——**在 feature worktree `git checkout main` 会被 git 拒绝**（ref 已被另一 worktree 占用）。所以切到持有 main 的 worktree（而非 checkout）：
⚠️ **切到持有 main 的 worktree 再 commit**：`gh pr merge --repo clowder-labs/clowder-ai --squash --delete-branch` 之后你仍在 feature worktree 上。直接 commit 会落到**已合并/已删的 feature branch**（或留脏工作树让 Step 8 fail-closed abort）。而且 worktree 开发场景下 `main` 由主仓 worktree 持有——**在 feature worktree `git checkout main` 会被 git 拒绝**（ref 已被另一 worktree 占用）。所以切到持有 main 的 worktree（而非 checkout）：

```bash
# 找到持有 main 的 worktree（通常是主仓 cat-cafe/），cd 过去做 doc-sync：
Expand Down Expand Up @@ -530,7 +540,7 @@ cd "$MAIN_WT" && git pull origin main # 取回刚 squash 的 commit，doc-sync
| Reviewer 放行？ | 搜索明确信号词 |
| P1/P2 清零？ | 检查 review 记录 |
| BACKLOG 更新？ | `grep '\[x\]' docs/ROADMAP.md` |
| 云端通过？ | `gh pr checks {PR}` |
| 云端通过？ | `gh pr checks {PR} --repo clowder-labs/clowder-ai` |
| Evidence validation 通过？(Step 6.9) | E1-E5 五项全绿（head 一致 + review 不 stale + provenance 闭合 + verdict passed + gate passed） |
| Feature doc 说真话？(pre-merge) | doc 标 ✅/打勾 AC 有代码支撑 + `node scripts/check-feature-truth.mjs` 绿 |
| 已合入状态记录？(post-merge) | feature doc Phase ✅ + AC 打勾 + Timeline 有 merged 记录 + Status 推进 |
Expand All @@ -547,8 +557,8 @@ cd "$MAIN_WT" && git pull origin main # 取回刚 squash 的 commit，doc-sync
| 修了 P1 不 re-trigger review | 修完 push 后**必须重新触发**remote review |
| cloud P1/P2 修完后又 @ 本地旧 reviewer 续签 | `headChangeCause=cloud-finding` → re-trigger cloud review + 等 PR tracking；本地 peer 不是 Stage ④ 常驻 gate |
| `pnpm gate` rebase / fixup 后沿用旧 review 直接 merge | 先对齐 `headRefOid`；**只要 HEAD 变了，先按 Review Provenance Matrix 判定 nextGateOwner** |
| 本地 `git rebase -i` 手动 squash | 用 `gh pr merge --squash`（GitHub 处理） |
| 本地 merge 后 `gh pr close` | `gh pr close` = 放弃，`gh pr merge` = 合入 |
| 本地 `git rebase -i` 手动 squash | 用 `gh pr merge --repo clowder-labs/clowder-ai --squash`（GitHub 处理） |
| 本地 merge 后 `gh pr close --repo clowder-labs/clowder-ai` | `gh pr close` = 放弃，`gh pr merge` = 合入（都按 Fork base trap 总规则带 `--repo`） |
| 不等remote review 直接合入 | 必须等 0 P1/P2 |
| 把截图/录屏/.pen 直接 commit 到仓库根目录 | Step 0.5 Root Artifact Guard 先拦截；先归档再开 PR |
| 跳过 evidence validation 直接 merge | Step 6.9 五项 E1-E5 全过才能进 Step 7；不组装 evidence = 不知道 review 是否 stale |
Expand Down Expand Up @@ -583,7 +593,7 @@ cd "$MAIN_WT" && git pull origin main # 取回刚 squash 的 commit，doc-sync
**动作**：**只发 `@codex review` 一行**重新触发（同 SHA 不需要新 commit）。

```bash
gh pr comment {PR_NUMBER} --body '@codex review'
gh pr comment {PR_NUMBER} --repo clowder-labs/clowder-ai --body '@codex review'
```

> 教训演进：2026-04-18 曾以为是"后台 bug / 没接单"，2026-04-20 PR #1300 确认根因是**详细格式触发 code-write 解析**。极简格式是唯一可靠触发方式（PR #1258 + PR #1300 两次实战验证）。
Expand Down Expand Up @@ -619,7 +629,7 @@ gh pr comment {PR_NUMBER} --body '@codex review'

**⚠️ 共享 API 池陷阱（F238 教训）**：同一 provider 的不同 model（Codex/GPT-5.4/GPT-5.5）共享 API 额度。降级必须跨 provider family（OpenAI → Anthropic），不能在同 provider 内换个体。

操作：`gh pr comment {PR} --body "..."` 用标准触发模板 @ 降级 reviewer（句柄查 `cat-config.json`）。
操作：`gh pr comment {PR} --repo clowder-labs/clowder-ai --body "..."` 用标准触发模板 @ 降级 reviewer（句柄查 `cat-config.json`）。

## 和其他 skill 的区别

Expand Down
Loading