gh-claimcheck
GitHub CLI extension: check an issue is really free before you work on it (no open PR, no claim, not moved), and find unclaimed issues in your project's dependencies
What XERJ indexed
Snapshot
The whole repository at commit 85068895c0. It is the newest commit on main.
Selected work
Licence
The repository
LICENSE file checked at the pinned commit; the author agreed to inclusion.
The XERJ corpus
The owner added it on hub.xerj.org after signing in with GitHub, on 2026-10-29. Same terms as the repository. Answers name the repo, the commit and the file:line.
selected for the XERJ Corpus Hublicence clearedsuggested use: adapt with attribution
beginner-friendlyclicontributingdeveloper-toolsduplicate-detectionfirst-timersgh-extensiongithub-cli
Example questions
- How does gh-claimcheck implement beginner-friendly?
- Show the cli code in gh-claimcheck.
Inside the indexed corpus
- 71 files, 259.5 KB in total, about 3.7 KB per file.
- On GitHub since 2026-10-22, last push 2026-10-26, 20 commits on main.
Licence on GitHub and in the corpus
GitHub reported MIT for RagedPanda/gh-claimcheck on 2026-10-31, and the LICENSE file at commit 85068895c0 was reviewed as MIT. They match, so answers from this corpus carry the same terms as the live repository.
Contributors
Ankur Dubey (@RagedPanda) has 4 selected repositories on the hub.
Their other repository pages: RagedPanda/hisab, RagedPanda/otp-qr, RagedPanda/time-sliced.
Using XERJ with gh-claimcheck
- Search an OpenAPI spec so an agent can find endpoints The hub files it under API design and specification.
- Index a reference library for a coding agent
- ripgrep vs a code index for coding agents: 30 tasks
- Best MCP servers for local code search in 2026, compared
The prompt
Paste it into your AI agent. It clones RagedPanda/gh-claimcheck at the pinned commit and indexes it on your machine.
Search the GitHub repository RagedPanda/gh-claimcheck with XERJ (https://hub.xerj.org/corpus/ragedpanda--gh-claimcheck). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/RagedPanda/gh-claimcheck gh-claimcheck && git -C gh-claimcheck checkout 85068895c08baa4fc31f78b0c07bf3834fe2d53f 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./gh-claimcheck --url http://127.0.0.1:9200 --prefix gh-claimcheck --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: MIT. Keep the copyright notice and credit the authors.
Related
Ankur DubeyAPI design and specification corporagrpc-gogopassexternal-secretsholt-oss/holtMehdiMamas/gh-runnersalok-108/phantom
Stats: GitHub API, fetched 2026-10-31. Snapshot: the git tree at the pinned commit. Selected work and consent: the XERJ registry.