gitcrawl

Search a local archived mirror of Brikko Studio GitHub issues and PRs.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill gitcrawl-brikkoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitcrawl
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/.agents/skills/gitcrawl
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill gitcrawl-brikkoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the slow, incomplete results of live GitHub search for Brikko Studio issue and PR triage by providing fast access to a local archived mirror of all threads, including closed ones, to surface duplicates and related work that may not appear in live search results.

Core Features & Use Cases

  • Local Archive Search: Quickly access open and closed Brikko Studio issue and PR threads from a local mirror, including historical context not easily found via live GitHub search.
  • Duplicate & Related Thread Discovery: Surface duplicate issue attempts and cluster related threads to avoid redundant work during triage.
  • Freshness Validation: Built-in checks to confirm the local archive is up to date before relying on its data for actionable decisions. Use Case: When triaging a new Brikko Studio bug report, use this skill to first check if the issue has already been reported, fixed in a closed PR, or related to existing work before spending time on live GitHub searches.

Quick Start

Use the gitcrawl skill to search the local Brikko Studio issue and PR archive for duplicates and related threads before checking live GitHub.

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 during triage faster than live search?

Duplicate issue identification is accelerated by searching a local archived mirror of all GitHub threads, including closed ones. This surfaces related work and duplicate reports that live GitHub search often misses, ensuring comprehensive triage.

What is the best way to access closed GitHub PR history for local repository maintenance?

Accessing closed GitHub PR history is done through a local archive mirror of all issue and PR threads. This allows maintainers to retrieve historical context and cluster related threads offline before acting on live data.

Does offline GitHub issue triage work for discovering related thread clusters?

Offline GitHub issue triage supports related thread clustering by scanning the local archived mirror. It groups duplicate reports and related work together, preventing redundant maintenance efforts during the triage workflow.

How do I validate local GitHub archive freshness before relying on offline search results?

Local GitHub archive freshness is validated using built-in checks within the triage workflow. These checks confirm the offline mirror is up to date before you rely on its data for actionable maintenance decisions.

Why does live GitHub search miss closed issues during repository maintenance?

Live GitHub search often returns incomplete results for triage because it misses closed issues and historical context. A local archived mirror captures all threads to ensure stale data detection and comprehensive duplicate discovery.