ghq-lookup

Prioritize local ghq clones for repository URLs before remote fetching.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/usadamasa/claude-config --skill ghq-lookup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghq-lookup
Source: https://github.com/usadamasa/claude-config/tree/main/dotclaude/skills/ghq-lookup
Command: npx skills add https://github.com/usadamasa/claude-config --skill ghq-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that when you refer to a repository, the AI prioritizes checking your local ghq managed clones before attempting to fetch from remote sources, significantly speeding up code analysis and reducing unnecessary network requests.

Core Features & Use Cases

  • Local-First Reference: Automatically checks for local ghq clones of a given repository URL.
  • URL Normalization: Handles various URL formats (HTTPS, SSH, with/without .git, subpaths) to match local paths.
  • Efficient Codebase Navigation: Prioritizes local files for faster context loading and better cost-efficiency.
  • Use Case: When asked to "review the code for the claude-config repository," this Skill will first look for ~/src/github.com/usadamasa/claude-config and use that if found, rather than fetching from GitHub.

Quick Start

Use the ghq-lookup skill to find the local clone for the repository URL https://github.com/usadamasa/claude-config.

Frequently Asked Questions about ghq-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I speed up local code analysis for a git repository?

To speed up local code analysis, the Skill prioritizes local git clones over remote fetching. By scanning pre-cloned repositories first, it reduces network requests and accelerates context loading for codebase reviews.

How does local clone lookup work for different GitHub and GitLab URL formats?

Local clone lookup works by normalizing various URL formats, including HTTPS, SSH, and paths with or without `.git`. The Skill translates repository URLs into standard local directory paths to match existing clones on your machine.

Do I need to use the ghq repository management tool to find local clones?

You need existing local clones managed by the ghq repository management tool. The Skill specifically scans for directories managed by ghq to locate existing copies of GitHub and GitLab repositories before fetching remotely.

What is the best way to analyze code without fetching from a remote git repository?

The best way to analyze code without fetching remotely is using a local-first reference approach. Scanning pre-cloned local repositories accelerates codebase navigation and improves cost-efficiency by avoiding unnecessary network requests.

What happens if a local ghq clone is not found for a repository URL?

If a local ghq clone is not found, the Skill resorts to remote fetching to retrieve the repository. This fallback ensures you can still access and analyze the codebase content even when a local copy is unavailable.