Search across public and private GitHub repositories using local copies and ripgrep, a text search tool. Find which repository or file contains an implementation, phrase, or setting, with results drawn from the default branch.
Full-text search across all of the user's GitHub repos (including private ones) using a local mirror and ripgrep. Use for "where did I put X", "which repo has X", or any search spanning the user's repos - gh search code / the REST API cannot reliably search private repos.
Review the instructions the agent will receive before you install.
GitHub's modern code search (the one that indexes private repos) is web-only; gh search code uses the legacy engine and often returns nothing for private repos. Instead, search a local mirror of all the user's repos - it covers the same content as GitHub's index (default branch, non-fork) and a full search takes milliseconds.
Find the bundled sync script (works for plugin installs and manual symlinks):
find ~/.claude ~/.codex -name "private-github-search-sync.sh" 2>/dev/null | sort -V | tail -1
Always refresh first - it exits instantly if the mirror was synced within the last hour, and takes ~15s otherwise (--force syncs regardless of age):
bash <script-path>
rg -il 'pattern' ~/repo-mirror/repos # which files
rg -in 'pattern' ~/repo-mirror/repos | head # matching lines
If ~/repo-mirror/owners.txt doesn't exist: ask the user which GitHub accounts to mirror (don't guess - they may manage several), write them one per line to ~/repo-mirror/owners.txt, then run the sync script in the background (initial clone takes a few minutes; needs gh auth with access to those accounts).
git log -S in a full clone or GitHub web search.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Investigate failed GitHub Actions jobs using logs and recent runs. Receive a report explaining the actual failure trigger, recurrence, any verified breaking commit, and existing pull requests that may fix the issue.
Create a new Claude Code session from the later half of the current conversation. Keep recent work while reducing conversation tokens, then receive a command to resume the copied session directly.
Create or update a HANDOFF.md document with the goal, progress, successful and failed approaches, and next steps. It gives an agent in a fresh conversation the context needed to continue the work.
Summarize popular Hacker News stories or find discussions on a specific topic. Get article highlights, scores, comment counts, and recurring discussion themes, including agreement, criticism, and related debates.
Create a new Claude Code session containing only the last quarter of the current conversation. Preserve the most recent work, reduce conversation tokens, and get a command to resume the copied session directly.
Retrieve Reddit posts and comments through a browser session for topic research. Search within communities, inspect popular or recent posts, and extract titles, scores, and replies, with procedures for handling blocked access and request limits.