agentleFS
moltbotmoltbot/moltbot/.agents/skills/gitcrawl/SKILL.md

gitcrawl

Skill393k starsChanged 7 days agoMITView on GitHub

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use local GitHub archives for discovery.

    line 19
  2. Very specific:

    Use bare PATH gh and narrow native JSON fields:

    line 38
  3. Very specific:

    Do not pass its --live/--cached flags or old field names to gh, restore an old Gitcrawl, bypass the existing Octopool shim, or change …

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

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:

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 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.

Download now (ZIP)

Trending

Quiet since March.about the whole repository

Dec 2025: 0 mentionsJan 2026: 48 mentionsFeb 2026: 5 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the moltbot/moltbot repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about moltbot/moltbot

The biggest 5 of 54 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 54

Talked about on GitHub, the web, Bluesky and Hacker News (54 times).

On GitHub · 32

27 more on GitHub

On the web · 14

9 more on the web

On Bluesky · 5

On Hacker News · 3

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.