github-navigator skill
✓ VerifiedPerforms GitHub operations including inspecting repositories, issues, pull requests, releases, and workflows using the gh CLI.
- GitHub stars
- 17
- Files
- 3
- Last commit
- Oct 31, 2026
- License
- MIT
- Allowed tools
- 7
What does the github-navigator skill do?
github-navigator performs GitHub operations including inspecting repositories, issues, pull requests, releases, and workflows using the gh CLI.
Summary generated from the skill's SKILL.md.
About the github-navigator skill
Managing and inspecting GitHub repositories directly from an AI agent is what this skill enables. Developers can use it to examine repository structures, pull requests, issues, releases, and GitHub Actions workflows. Instead of relying on generic web fetching, the agent uses the gh CLI and git to interact with GitHub content, making it a specialized tool for codebase analysis and repository management.
When an agent encounters a GitHub URL or a repository path like owner/repo, it loads this skill to perform tasks such as listing directory contents via the gh api or inspecting specific metadata. For deep architectural analysis, the skill can clone a repository with depth 1 to a local directory to scan for tech stack signals like package.json or go.mod. It relies on the gh CLI, git, and network access to function.
This tool is designed for precision, prioritizing dedicated subcommands like gh issue or gh pr over raw API calls. It includes safety guardrails that require confirmation before executing destructive actions such as merging pull requests or deleting repositories.
What an agent can do with it
- 1Analyze repository architectureAsk the agent to understand the tech stack and directory structure of a specific repository.
- 2Inspect pull requests and issuesRequest a summary of recent pull requests or open issues within a project.
- 3Monitor GitHub Actions workflowsCheck the status of recent workflow runs or inspect automation configurations.
- 4Retrieve raw file contentFetch the contents of a specific file within a repository using the API.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the github-navigator skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the github-navigator skill in Plugin
/plugin marketplace add arvindand/agent-skills /plugin install agent-skills@arvindand-skills
Install the github-navigator skill in Claude Code
~/.claude/skills/github-navigator/SKILL.md
$ npx degit arvindand/agent-skills/skills/github-navigator ~/.claude/skills/github-navigatorInstall the github-navigator skill in Claude Code (project)
.claude/skills/github-navigator/SKILL.md
$ npx degit arvindand/agent-skills/skills/github-navigator .claude/skills/github-navigatorInstall the github-navigator skill in Codex
~/.agents/skills/github-navigator/SKILL.md
$ npx degit arvindand/agent-skills/skills/github-navigator ~/.agents/skills/github-navigatorInstall the github-navigator skill in Gemini CLI
~/.gemini/skills/github-navigator/SKILL.md
$ npx degit arvindand/agent-skills/skills/github-navigator ~/.gemini/skills/github-navigatorInstall the github-navigator skill in Claude.ai
npx degit arvindand/agent-skills/skills/github-navigator github-navigator && zip -r github-navigator.zip github-navigator # claude.ai → Customize → Skills → + → Create skill → Upload a skill → github-navigator.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablearvindand/agent-skills/skills/github-navigator is public and reachablegithub.com/arvindand/agent-skills/tree/HEAD/skills/github-na ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-31github.com/arvindand/agent-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/arvindand/agent-skills/blob/HEAD/skills/github-na ↗Pass
- Pre-approved tools are scopedPre-approved: Bash(gh:*), Bash(git, clone:*), Read, Glob, Grep, …github.com/arvindand/agent-skills/blob/HEAD/skills/github-na ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 112 linesgithub.com/arvindand/agent-skills/blob/HEAD/skills/github-na ↗Pass
SKILL.md
View on GitHubGitHub Navigator
Use gh for GitHub work. Prefer command discovery over memorizing flags.
This is an execution skill. Use gh instead of generic web fetching for GitHub tasks, inspect gh --help when syntax is uncertain, then execute with tight guardrails. Keep the main flow lean and load REFERENCES.md only when you need concrete examples, installation steps, or GraphQL details.
When to Use
Activate when:
- the user gives a
github.comURL - the user names a repo path like
facebook/reactorowner/repo - the user asks about repository files, issues, PRs, releases, workflows, or metadata
- the user wants to understand the architecture or structure of a GitHub-hosted codebase
Core Rules
- Always prefer
ghoverWebFetchfor GitHub content and operations. - Use
gh apifor raw file content, directory listings, and API-only endpoints. - Use
ghsubcommands (issue,pr,release,run,workflow,repo) when a dedicated command exists. - Use
gh <domain> --helpbefore guessing flags or subcommands. - Limit each command pattern to 2 attempts; if it still fails, stop and report the error.
Command Routing
| User Intent | Primary Command Path |
|---|---|
| fetch file or list directory | gh api repos/OWNER/REPO/contents/... |
| inspect issues | gh issue ... |
| inspect pull requests | gh pr ... |
| inspect releases | gh release ... |
| inspect Actions runs or workflows | gh run ... or gh workflow ... |
| inspect repo metadata or clone/fork | gh repo ... |
| endpoints without a dedicated subcommand | gh api ... |
Use dedicated subcommands first. Fall back to gh api only when needed.
Execution Pattern
- Identify the command domain from the request.
- Check the relevant help output if the exact syntax is not already obvious.
- Substitute the user's repo, path, issue number, PR number, or other arguments.
- Run the command.
- If it fails, adjust once based on the error message.
- If it fails again, stop and report the error instead of trying blind variations.
Deep Analysis Mode
When the user wants to understand a codebase deeply, clone it locally for inspection instead of making many remote API calls.
Default flow:
-
Clone with depth 1 to
/tmp/github-navigator/OWNER-REPO/git clone --depth 1 https://github.com/OWNER/REPO.git /tmp/github-navigator/OWNER-REPO -
Inspect the repository for:
- tech stack signals (
package.json,go.mod,Cargo.toml,pom.xml,requirements.txt, etc.) - high-level directory structure
- entry points and primary modules
- README, docs, examples, and contribution files
- architectural patterns worth calling out
- tech stack signals (
-
Summarize the findings in plain language.
-
Keep the clone for follow-up questions unless cleanup is requested.
Use a full clone only if the user explicitly needs commit history or deeper git analysis.
Safety
Always confirm before executing state-changing or destructive commands, including:
- creating, closing, or reopening issues
- creating, merging, or closing pull requests
- deleting, archiving, or transferring repositories
- setting secrets or triggering workflows
- any use of
--force,--yes, or similar bypass flags
Authentication and Recovery
- Check
gh auth statuswhen the task touches private repos or write operations. - Use
gh auth loginif the client is not authenticated. - If permissions are insufficient, use
gh auth refresh -s repo -s workflow -s read:orgas appropriate. - If a command fails, read the error, check help, retry once, then stop.
- If
ghis not installed, point the user to REFERENCES.md for installation guidance.
Reference Handoff
Use REFERENCES.md when you need:
- concrete example commands for common tasks
- install and auth setup details
- troubleshooting reminders
- GraphQL examples or other lower-frequency patterns
License: MIT See also: REFERENCES.md
Files in this skill
3github-navigator skill questions
How do I install the github-navigator skill in Claude Code?
Run npx degit arvindand/agent-skills/skills/github-navigator ~/.claude/skills/github-navigator. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the github-navigator skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
When should I use this skill instead of WebFetch?
You should use this skill for any github.com URL or repository path to inspect files, issues, pull requests, or repository structure.
How can I perform a deep analysis of a codebase?
For deep analysis, the skill clones the repository locally with depth 1 to a temporary directory to inspect the tech stack, directory structure, and entry points.
What should I do if I encounter permission issues with private repositories?
You should check the authentication status with gh auth status and use gh auth login or refresh permissions as needed.