gitcrawl

Search local OpenClaw issue and pull request archives to identify duplicates.

Updated Jun 18, 2026

Search Tags:#automation #github #search #triage #issue-tracking #openclaw

Ready to run

npx skills add https://github.com/wangqianCAI/OBI --skill gitcrawl-wangqiancai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitcrawl
Source: https://github.com/wangqianCAI/OBI/tree/main/.agents/skills/gitcrawl
Command: npx skills add https://github.com/wangqianCAI/OBI --skill gitcrawl-wangqiancai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the inefficiency of performing repetitive live GitHub searches when triaging issues and pull requests, providing a faster, local-first discovery layer for historical context.

Core Features & Use Cases

Duplicate Discovery: Quickly identify if a reported issue or PR has been previously attempted or discussed.
Thread Clustering: Group related issues and PRs to understand the broader scope of a bug or feature request.
Local Mirroring: Maintain a local, searchable archive of the OpenClaw repository to ensure fast access to closed threads and historical data.

Quick Start

Use the gitcrawl skill to search for related issues and pull requests for the current task by querying the local archive.

Frequently Asked Questions about gitcrawl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find duplicate GitHub issues and related pull requests during triage?▼

To find duplicate GitHub issues during triage, you can search a local archive of historical repository threads to identify related pull requests and previously discussed topics before performing live operations.

What is the best way to search closed GitHub issues for historical context without live API queries?▼

The best way to search closed GitHub issues for historical context is by maintaining a local searchable archive, which provides a faster, local-first discovery layer compared to repetitive live GitHub searches.

How does local issue triage work for grouping related threads in a repository?▼

Local issue triage works by querying a synchronized local store of repository data to perform thread clustering, grouping related issues and pull requests to understand the broader scope of bugs or features.

Do I need a specific binary to search local archives of OpenClaw issues?▼

Yes, searching local archives of OpenClaw issues requires the gitcrawl binary and a synchronized local store to function properly as a candidate-discovery layer for maintainer workflows.

Why should I use a local archive instead of live GitHub search for issue triage?▼

You should use a local archive instead of live GitHub search to solve the inefficiency of performing repetitive live queries, ensuring fast access to closed threads and historical data.

Can I group related feature requests and bug reports using local repository history?▼

Yes, you can group related feature requests and bug reports by applying cluster analysis to your local repository history, allowing you to understand the broader scope of ongoing issues.