一键导入
ghq-lookup
Use when you need to read, explore, or reference source code from any Git repository. Use before cloning manually or asking the user for a path.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when you need to read, explore, or reference source code from any Git repository. Use before cloning manually or asking the user for a path.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when working with JIRA from the terminal. Use when asked to look up, create, update, transition, assign, or comment on JIRA issues. Use for sprint or epic operations.
Use this skill whenever the user wants to commit changes, stage files, write a commit message, or run git commit — even if they just say "commit this", "save my changes", or "make a commit". Guides writing well-structured commit messages following the Conventional Commits specification, enforcing scope rules from .conform.yaml, protecting main/master branches, and ensuring clean staging hygiene before every commit.
Use when working with flake-parts or dev-flake — structuring flakes, defining perSystem outputs, writing reusable flake modules, using withSystem or moduleWithSystem, exporting flakeModules, setting up dev environments with dev-flake, or debugging flake-parts evaluation.
Use when writing, editing, or reviewing Nix code — including NixOS modules, Home Manager configuration, packages, and overlays. Covers Nix coding style, module system patterns, common lib functions, and tooling (nixfmt, deadnix, statix). For flake-parts-specific patterns use the flake-parts skill instead.
| name | ghq-lookup |
| description | Use when you need to read, explore, or reference source code from any Git repository. Use before cloning manually or asking the user for a path. |
ghq manages remote repository clones under a single root, organized as
<root>/<host>/<org>/<repo>. Use it to find and fetch source code instead
of cloning manually.
ghq list -p <query> — partial match, prints full paths. Use that path directly if found.ghq get <host>/<org>/<repo> # e.g. ghq get github.com/org/repo
ghq get <org>/<repo> # defaults to github.com
ghq get -p <org>/<repo> # clone via SSH
ghq get --shallow <org>/<repo> # shallow clone for large repos
Then use ghq list -p <query> to get the full path.| Task | Command |
|---|---|
| Check if repo exists / get path | ghq list -p <query> |
| Fetch a repo | ghq get <host>/<org>/<repo> |
| Fetch via SSH | ghq get -p <org>/<repo> |
| Shallow clone | ghq get --shallow <org>/<repo> |
| Update existing repo | ghq get -u <org>/<repo> |