promisingcoder Gitcrawl
Use local GitHub issue/PR archives before live GitHub search. Check freshness first:
gitcrawl doctor --json
Find candidates:
gitcrawl threads promisingcoder/marketingclaw --numbers <issue-or-pr-number> --include-closed --json
gitcrawl neighbors promisingcoder/marketingclaw --number <issue-or-pr-number> --limit 12 --json
gitcrawl search issues "query" -R promisingcoder/marketingclaw --state open --json number,title,url
gitcrawl clusters promisingcoder/marketingclaw --sort size --min-size 5
gitcrawl cluster-detail promisingcoder/marketingclaw --id <cluster-id>
For PR triage, start cached and go live only before mutation/merge decisions:
gitcrawl gh pr status <number-or-url> -R promisingcoder/marketingclaw --compact
gitcrawl gh pr view <number-or-url> -R promisingcoder/marketingclaw --json number,title,state,url,isDraft,headRef,headSha
gitcrawl gh --live pr status <number-or-url> -R promisingcoder/marketingclaw --compact
Use live gh plus checkout proof before commenting, labeling, closing, reopening, merging, or filing a PR review:
gh pr view <number> --json number,title,state,mergedAt,body,files,comments,reviews,statusCheckRollup
gh issue view <number> --json number,title,state,body,comments,closedAt
Report absolute dates, repo names, issue/PR numbers, cluster ids, and source gaps. Do not close/label from similarity alone; require matching intent plus live verification.