Search local GitHub issue and PR archives for triage.
npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill gitcrawl
Please help me install this Agent Skill. Skill: gitcrawl Source: https://github.com/p-sree-sai-pavan/P.A.R.K.E.R/tree/main/gateway/.agents/skills/gitcrawl Command: npx skills add https://github.com/p-sree-sai-pavan/P.A.R.K.E.R --skill gitcrawl
Gitcrawl helps teams reason about historical GitHub issues and PRs by keeping a local archive and indexing past discussions, enabling faster and more reliable triage without relying solely on live queries.
Sync the local archive with gitcrawl doctor and run a search for a repository.
High-intent search queries and answers about installing and using this skill.
You can search local GitHub issue archives offline by syncing a local repository archive and querying historical discussions, threads, and clusters to improve triage accuracy without relying on live API requests. This accelerates duplicate detection and status checks across multiple repositories.
The best way to detect duplicate GitHub threads is by indexing local archive history to surface related conversations and cluster reasoning. This approach surfaces neighboring discussions across repositories, helping teams avoid rework during triage sessions before checking live PR status.
You check live GitHub PR status during offline review by integrating gh commands via a gh-shim. This ensures your triage decisions remain grounded in up-to-date context, syncing freshness checks alongside your local archive search to validate historical discussion data.
Yes, you need an integrated local GitHub archive and tooling to query threads, neighbors, and clusters. The offline archive-first workflow requires this local sync to accelerate triage decisions and detect duplicates before running live gh commands for PR status validation.
Yes, you can sync freshness checks for multiple GitHub repositories using the gitcrawl doctor command. This validates your local archive sync state, ensuring historical issue and PR discussions are current and reliable before triage decisions are made.
You should avoid relying solely on offline GitHub archive search when real-time code review context is critical. While local archives accelerate duplicate detection and cluster reasoning, always validate with live gh commands and PR status checks to ensure decisions reflect the latest repository state.
wuv-dreamguideManage GitHub issues, PRs, CI runs, and reviews via gh CLI.
freire19Retrieve GitHub repository, issue, pull request, and CI data via gh CLI.
bradtaylorsfSearch GitHub issues and assess similarity to detect duplicates.
brikkoAISearch a local archived mirror of Brikko Studio GitHub issues and PRs.
