exploring-reposlisted

# Explore Public Repositories Use public sources and local clones. Do not assume specialized repo-wiki tools exist. ## Workflow 1. Normalize the repo as `owner/name`. 2. Check if the repo is already cloned locally. 3. If not, ask before cloning large repos. For quick reads, prefer GitHub URLs or `gh repo view`. 4. Use the runtime's web tools for public docs, README context, release notes, or architecture articles. 5. Use `gh` or a shallow clone for code structure when needed. 6. For cloned-repo exploration, use scoped local tools: `fd` for files and `rg` for text. Use dedicated codebase-analysis tooling for structural or architecture evidence when needed. 7. Map architecture from files, not reputation. 8. Use `looking-up-docs` for library API docs, not repo architecture. ## Commands ```bash gh repo view owner/name --json name,description,homepageUrl,repositoryTopics rg -n 'architecture|design|package|module|cmd|src' README.md docs 2>/dev/null fd 'README|CONTRIBUTING|docs|cmd|src|packages|internal' ``` For a temporary clone: ```bash git clone --depth=1 https://github.com/owner/name /tmp/name-repo ``` ## Failure Handling - Repo not found or private: report the `gh` error, ask the user to confirm the `owner/name` slug or check access. - `gh` not installed: fall back to `git clone --depth=1` and available web search for public docs; note the limitation. - Clone too large (>500 MB): warn before cloning, offer shallow clone or `gh repo view` summary only. ## Output