GitHub operations via gh CLI. CRITICAL: Always use instead of WebFetch for ANY github.com URL. Use when user provides GitHub URL, says 'facebook/react', 'show README', 'list issues', 'check PR', 'clone repo', 'analyze this repo', 'understand the architecture', 'how is X structured', 'explore the codebase'. For deep analysis of external repos, clones locally.
View on GitHubskills/github-navigator/SKILL.md
January 20, 2026
Select agents to install to:
npx add-skill https://github.com/arvindand/agent-skills/blob/main/skills/github-navigator/SKILL.md -a claude-code --skill github-navigatorInstallation paths:
.claude/skills/github-navigator/# GitHub Navigator Uses gh CLI for **all** GitHub operations. Teaches discovery pattern via `gh --help`. **Requirements:** `gh` CLI installed and authenticated. ## Core Principle **One pattern for everything:** 0. **Verify** gh CLI is installed and authenticated (first use only) 1. **Identify** command domain (files, issues, PRs, releases, etc.) 2. **Discover** usage via `gh <command> --help` or `gh api --help` 3. **Apply** pattern to user's specific request 4. **Execute** with max 2 attempts, then STOP ## When to Use **ALWAYS use this skill when:** - User provides a GitHub URL (any `github.com/` link) - User asks about GitHub repositories, issues, PRs, releases - User mentions repo paths like "facebook/react" - User wants GitHub information or operations **Common triggers:** - "Show me the README from facebook/react" - "List open issues in vercel/next.js" - "What's in the packages/ directory?" - "Check latest release for react" - "View PR #123 in cli/cli" ## Deep Analysis Mode When user wants to **understand a codebase deeply** (not just fetch a single file), clone the repository locally for comprehensive analysis. **Trigger phrases:** - "analyze this repo" - "understand the architecture" - "how is X structured" - "explore the codebase" - "give me an overview of" - "what patterns does X use" - "how does this project work" **Workflow:** 1. Clone to `/tmp/github-navigator/<owner>-<repo>/` ```bash git clone --depth 1 https://github.com/OWNER/REPO.git /tmp/github-navigator/OWNER-REPO ``` 2. Analyze the codebase: - **Tech stack detection**: Look for package.json, go.mod, Cargo.toml, pom.xml, requirements.txt, etc. - **Directory structure**: Map out the main directories and their purposes - **Entry points**: Find main files, index files, app entry points - **Patterns**: Identify architectural patterns (MVC, microservices, monorepo, etc.) - **Key files**: README, CONTRIBUTING, docs/, examples/ 3. Provide comprehensive summary wit