search-github

To find GitHub repositories by actual intent rather than literal keywords, apply multiple search strategies using the gh CLI to surface relevant projects, then deduplicate results against existing clones to ensure a concise, prioritized discovery list.

The best way to generate a clone plan is to curate discovered GitHub repositories into structured will-clone, already-have, and skipped sections, ensuring the plan respects cloning caps and records readiness for downstream actions.

To avoid cloning duplicate GitHub repositories, deduplicate new search results against your existing local clones before generating a final clone plan, categorizing matches into an already-have section to prevent redundant downloads.

Yes, you can generate a concise 1-2 sentence context summary for each discovered GitHub repository, providing enough context to guide your downstream actions and prioritize your actual clone plan effectively.

Yes, to search GitHub repositories by intent using this strategy-driven approach, the gh CLI must be installed and authenticated in your environment to execute the underlying queries and surface relevant projects.

Limitations when searching for GitHub repositories include enforced cloning caps to restrict the number of downloaded repos and saved discovery records that must be managed for downstream actions to avoid exceeding local storage capacity.