Exploring Repositories

Explore external repositories without cluttering the active workspace.

Use this skill for repository content exploration: reading files, grepping code, inspecting history, and comparing implementation details. For GitHub operations such as issues, PRs, actions, secrets, releases, or repo metadata, use gh directly instead.

Lookup order

1. Identify the target repository URL, owner, name, and branch if the user provided one.

2. Check existing direct-child checkouts first:

   ~/projects/work/<repo>
   ~/projects/personal/<repo>
   

   Confirm each candidate is a Git checkout and that git -C <candidate> remote get-url origin matches the requested repository. Do not reuse a directory based on its name alone. If both locations match, report the ambiguity before inspecting either one.