gitcrawl

Search local GitHub issue and PR archives before live GitHub triage.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill gitcrawl-jerome-prakash-l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitcrawl
Source: https://github.com/JEROME-PRAKASH-L/openclaw/tree/main/.agents/skills/gitcrawl
Command: npx skills add https://github.com/JEROME-PRAKASH-L/openclaw --skill gitcrawl-jerome-prakash-l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Live GitHub searches are slow and rate-limited when triaging large issue and PR backlogs. This Skill lets you query a local archive of OpenClaw issues and PRs first, checking freshness and finding duplicates before making any live GitHub calls. ## Core Features & Use Cases - Local Archive Search: Query cached issues and PRs with gitcrawl search, threads, and neighbors commands, with freshness checks via gitcrawl doctor. - Duplicate Detection: Find duplicate clusters with gitcrawl clusters and inspect them with cluster-detail to consolidate related reports. - Safe PR Triage: Use the cached gh shim for status checks, then escalate to live gh verification before commenting, labeling, closing, or merging. - Use Case: When a new bug report arrives, search the local archive for related threads and duplicate clusters, then verify with live GitHub data before deciding to close it as a duplicate. ## Quick Start Ask the assistant to check archive freshness with gitcrawl doctor, then search the local OpenClaw issue archive for threads related to a given issue number.

Frequently Asked Questions about gitcrawl

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

FAQPage Schema
How do I search GitHub issues without hitting rate limits?

Use gitcrawl to query a local archive of issues and PRs instead of the live GitHub API. Run gitcrawl search issues with your query and repo, and check archive freshness first with gitcrawl doctor --json.

How do I find duplicate GitHub issues in a large repository?

Run gitcrawl clusters on the repository to list duplicate clusters sorted by size, then inspect a specific group with gitcrawl cluster-detail. Verify matches with live gh issue view before closing anything as a duplicate.

How do I check PR status before merging with gitcrawl?

Start with the cached shim using gitcrawl gh pr status for a compact view, then run gitcrawl gh --live pr status or gh pr view with JSON fields to confirm current state before merging or reviewing.

Can gitcrawl close or label issues automatically?

No. The Skill explicitly requires live gh verification plus checkout proof before commenting, labeling, closing, reopening, merging, or filing a review. Similarity alone is never sufficient for mutations.

What are the requirements to install gitcrawl?

The gitcrawl binary is required and can be installed via Go with go install github.com/openclaw/gitcrawl/cmd/gitcrawl@latest. The gh CLI is also used for live verification steps.