Gitcrawl
GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Gitcrawl when an AI agent needs a reusable SKILL.md workflow for this job: GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.
When not to use it
Skip Gitcrawl when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/gitcrawl # Save SKILL.md to ~/.claude/skills/gitcrawl/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/gitcrawl/SKILL.md. For a shared project, commit the folder at .claude/skills/gitcrawl/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Gitcrawl skill for this task: Use Gitcrawl when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 72/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Gitcrawl
Use local GitHub archives for discovery; verify current GitHub state before a maintainer decision or public mutation. Check freshness and configured database paths with `gitcrawl doctor --json`.
```bash gitcrawl threads owner/repo --numbers <number> --include-closed --json gitcrawl neighbors owner/repo --number <number> --limit 12 --json gitcrawl search issues "query" -R owner/repo --state open --json number,title,url gitcrawl clusters owner/repo --sort size --min-size 5 gitcrawl cluster-detail owner/repo --id <cluster-id> ```
For stale results, use a bounded `--sync-if-stale 5m` search or targeted `gitcrawl sync owner/repo --numbers 123,456 --with pr-details`. The latter hydrates local PR files, commits, checks, workflow runs, and review-thread resolution; it does not populate the separate GitHub CLI cache.
## Current GitHub State
Use bare PATH `gh` and narrow native JSON fields:
```bash gh pr view <number> -R owner/repo --json number,title,state,url,isDraft,headRefName,headRefOid gh pr checks <number> -R owner/repo --json name,state,bucket,link gh issue view <number> -R owner/repo --json number,title,state,closedAt,url ```
`gitcrawl gh` was removed. Its exit 2 is a migration notice, not an auth failure. Do not pass its `--live`/`--cached` flags or old field names to `gh`, restore an old Gitcrawl, bypass the existing Octopool shim, or change auth/PATH/config to repair that removed command. Octopool owns the shared `gh` cache; Gitcrawl owns the local archive. See the [upstream migration guide](https://github.com/openclaw/gitcrawl/blob/main/docs/gh-shim.md) when setting up or diagnosing that handoff.
## Archive Boundaries
Archive state and similarity are candidate evidence, not proof of a duplicate or resolved issue. Report repository, issue/PR numbers, absolute date spans, cluster IDs, freshness, and known gaps. `close-thread`, `close-cluster`, and canonical-member choices are local overrides; they do not mutate GitHub. Public mutations use authorized `gh` workflows and checkout proof.
For exact archive counts, Gitcrawl has no `sql` subcommand. Resolve `.db_path` from `doctor --json` and use `sqlite3 -readonly`; do not modify database rows instead of using the maintainer commands. For Gitcrawl implementation work, verify the checkout remote is `openclaw/gitcrawl` and use its own instructions.
Intended uses
- Use Gitcrawl when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.