ghq-repo-placement

Resolve Git repository placement with ghq for cloning and workflows.

1|1|Updated Jul 24, 2014

Search Tags:#git #repository management #ghq #repository placement #clone strategy

Ready to run

npx skills add https://github.com/rmanzoku/dotfiles --skill ghq-repo-placement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ghq-repo-placement
Source: https://github.com/rmanzoku/dotfiles/tree/main/skills/ghq-repo-placement
Command: npx skills add https://github.com/rmanzoku/dotfiles --skill ghq-repo-placement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ghq, and includes scripts (resource) components.

What problem does it solve?

This Skill resolves the issue of inconsistent repository placement when users encounter Git repository URLs, cloning requests, or questions about repository placement, promoting efficient and structured workflows.

Core Features & Use Cases

ghq-based Placement: Determines optimal local placement of Git repositories using ghq.
Project-specific Rules: Follows explicit project-local intent when vendor, submodules, or test fixtures are required.
Fallback Mechanism: Offers a fallback to a standard path if ghq is not available.

Quick Start

Use the ghq-repo-placement skill to clone the repository at 'https://github.com/<owner>/<repo>.git'.

Frequently Asked Questions about ghq-repo-placement

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

FAQPage Schema

How do I manage Git repository placement for consistent local storage?▼

Git repository placement determines where cloned code resides locally. Using ghq resolves URLs into a structured directory hierarchy, ensuring consistent local storage for vendor dependencies, submodules, and temporary checkouts.

What is the best way to clone a Git repository URL using ghq?▼

To clone a Git repository URL efficiently, pass the URL to ghq. This resolves the remote path and automatically places the cloned repository into the correct local directory structure without manual path management.

Do I need ghq installed to manage my repository clone strategy?▼

You need ghq installed for optimal repository placement, but a fallback mechanism exists. If ghq is not available, the system falls back to a standard path to maintain your clone strategy workflow.

Can I use ghq for repository placement with project-specific rules like submodules?▼

Yes, ghq repository placement supports project-specific rules. It follows explicit project-local intent to ensure proper directory placement for vendor dependencies, submodules, and test fixtures.

Why does my Git clone strategy result in inconsistent local storage paths?▼

Inconsistent local storage paths happen when cloning without a structured placement tool. Resolving repository URLs with ghq enforces a unified directory hierarchy, eliminating scattered clones and optimizing storage.

What are the limitations of using ghq for repository management?▼

The main limitation of ghq for repository management is its dependency on the tool being installed. However, a fallback placement logic activates when ghq is missing, preventing workflow disruption.