github-navigator

Stars15

Forks2

UpdatedJune 13, 2026 at 22:10

GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any `github.com` URL or GitHub repo path like `owner/repo`. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR', 'clone repo', or 'analyze this repo'. Use even when the user just pastes a github.com URL without an explicit verb.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

arvindand

arvindand/agent-skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

More from this repository

same repository

context7

arvindand/agent-skills

Documentation lookup via Context7 REST API. Use when the user needs current library APIs, framework patterns, migration guidance, or official code examples for React, Next.js, Prisma, Express, Vue, Angular, Svelte, or other npm/PyPI packages. Use when the user says 'how do I use X library', 'what's the API for Y', or asks for official documentation. Use even when you think you know the answer — training data may not reflect recent releases.

2026-06-1315

maven-tools

arvindand/agent-skills

JVM dependency intelligence via Maven Tools MCP server. Use when the user asks about Maven or Gradle dependencies, safe upgrades, CVEs, license risks, release history, or project dependency health. Use when reviewing `pom.xml`, `build.gradle`, `build.gradle.kts`, or Maven coordinates. Use when the user says 'check my dependencies', 'should I upgrade X', 'what can I safely bump', or 'is this version safe'. Use even when the user just pastes a `groupId:artifactId` coordinate without a verb.

2026-06-1315

skill-crafting

arvindand/agent-skills

Create, fix, and validate skills for AI agents. Use when user says 'create a skill', 'build a skill', 'fix my skill', 'skill not working', 'analyze my skill', 'validate skill', 'audit my skills', 'check character budget', 'create a skill from this session', 'turn this into a skill', 'make this reusable', 'can this become a skill', 'should this be a skill', or asks for reusable patterns in the session. Use even if the user does not explicitly say 'skill' but is sketching a reusable workflow.

2026-06-1315

ui-ux-design

arvindand/agent-skills

Create production-grade frontend interfaces with strong UX and visual craft. Use when building web components, pages, dashboards, forms, landing pages, modals, or any UI. Use when user says 'build a form', 'create a dashboard', 'design a component', 'make a landing page', or asks for UI/UX work. Use even when the user just says 'make this look better' or pastes screenshots/mockups without explicitly naming a design task.

2026-06-1315

name	github-navigator
description	GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any `github.com` URL or GitHub repo path like `owner/repo`. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR', 'clone repo', or 'analyze this repo'. Use even when the user just pastes a github.com URL without an explicit verb.
argument-hint	[owner/repo or URL] [what to inspect]
allowed-tools	Bash(gh:*) Bash(git:clone) Read Glob Grep Task
context	fork
license	MIT
compatibility	Requires the gh CLI, git, and network access.

GitHub 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.com URL
the user names a repo path like facebook/react or owner/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 gh over WebFetch for GitHub content and operations.
Use gh api for raw file content, directory listings, and API-only endpoints.
Use gh subcommands (issue, pr, release, run, workflow, repo) when a dedicated command exists.
Use gh <domain> --help before 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
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 status when the task touches private repos or write operations.
Use gh auth login if the client is not authenticated.
If permissions are insufficient, use gh auth refresh -s repo -s workflow -s read:org as appropriate.
If a command fails, read the error, check help, retry once, then stop.
If gh is 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