gitcrawl

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Gitcrawl

Use this skill before live GitHub search when triaging OpenClaw issues or PRs.

gitcrawl

is the local candidate-discovery layer. It is fast, includes open and closed threads, and can surface duplicate attempts, related issues, and already-landed fixes. It is not the final source of truth for comments, labels, merges, closes, or current CI.

在处理OpenClaw议题（issue）或拉取请求（PR）时，可在使用实时GitHub搜索前先使用此技能。

gitcrawl

是本地候选内容发现层，它速度快，包含开放和已关闭的线程，能够找出重复尝试、相关议题以及已落地的修复方案。但它并非评论、标签、合并、关闭状态或当前CI的最终可信来源。

Default Flow

默认流程

Check local state:

bash

gitcrawl doctor --json

Read the target from the local archive:

bash

gitcrawl threads openclaw/openclaw --numbers <issue-or-pr-number> --include-closed --json

Find related candidates:

bash

gitcrawl neighbors openclaw/openclaw --number <issue-or-pr-number> --limit 12 --json
gitcrawl search openclaw/openclaw --query "<scope or title keywords>" --mode hybrid --limit 20 --json

Inspect relevant clusters:

bash

gitcrawl cluster-detail openclaw/openclaw --id <cluster-id> --member-limit 20 --body-chars 280 --json

Verify anything actionable with live GitHub and the checkout:

bash

gh pr view <number> --json number,title,state,mergedAt,body,files,comments,reviews,statusCheckRollup
gh issue view <number> --json number,title,state,body,comments,closedAt

检查本地状态：

bash

gitcrawl doctor --json

从本地归档中读取目标内容：

bash

gitcrawl threads openclaw/openclaw --numbers <issue-or-pr-number> --include-closed --json

查找相关候选内容：

bash

gitcrawl neighbors openclaw/openclaw --number <issue-or-pr-number> --limit 12 --json
gitcrawl search openclaw/openclaw --query "<scope or title keywords>" --mode hybrid --limit 20 --json

检查相关聚类：

bash

gitcrawl cluster-detail openclaw/openclaw --id <cluster-id> --member-limit 20 --body-chars 280 --json

通过实时GitHub和本地检查验证可执行操作：

bash

gh pr view <number> --json number,title,state,mergedAt,body,files,comments,reviews,statusCheckRollup
gh issue view <number> --json number,title,state,body,comments,closedAt

Freshness Rules

新鲜度规则

Treat
```
gitcrawl
```
as stale if
```
doctor
```
shows no target thread, an old
```
last_sync_at
```
, missing embeddings for neighbor/search commands, or a clearly wrong open/closed state.
If stale data blocks the decision, refresh the portable store first:

bash

gitcrawl init --portable-store git@github.com:openclaw/gitcrawl-store.git --json

Run expensive update commands such as
```
gitcrawl sync --include-comments
```
only when the user asked to update the local store or stale data is blocking the decision.
The sync default is all GitHub thread states; pass
```
--state open
```
,
```
--state closed
```
, or
```
--state all
```
only when a task requires a narrower or explicit scope.

如果
```
doctor
```
显示无目标线程、
```
last_sync_at
```
时间过久、邻居/搜索命令缺少嵌入信息，或开放/关闭状态明显错误，则认为
```
gitcrawl
```
数据已过期。
如果过期数据影响决策，需先刷新可移植存储：

bash

gitcrawl init --portable-store git@github.com:openclaw/gitcrawl-store.git --json

仅当用户要求更新本地存储，或过期数据阻碍决策时，才运行
```
gitcrawl sync --include-comments
```
这类资源消耗较大的更新命令。
同步默认包含所有GitHub线程状态；仅当任务需要更窄或明确的范围时，才传入
```
--state open
```
、
```
--state closed
```
或
```
--state all
```
参数。

Boundaries

使用边界

Use
```
gitcrawl
```
for candidates, clusters, and historical context.
Use
```
gh
```
,
```
gh api
```
, and the current checkout for live state before commenting, labeling, closing, reopening, merging, or filing a PR review.
Do not close or label based only on
```
gitcrawl
```
similarity. Require matching problem intent plus live verification.
If
```
gitcrawl
```
is unavailable, say so and fall back to targeted
```
gh search
```
rather than blocking normal maintainer work.

使用
```
gitcrawl
```
获取候选内容、聚类信息和历史上下文。
在评论、打标签、关闭、重新开放、合并或提交PR评审前，使用
```
gh
```
、
```
gh api
```
和当前本地检查获取实时状态。
不可仅基于
```
gitcrawl
```
的相似度就关闭议题或打标签，需匹配问题意图并进行实时验证。
如果
```
gitcrawl
```
不可用，需告知用户并改用针对性的
```
gh search
```
，避免阻碍维护人员的正常工作。