gh-cli — community gh-cli, claude-plugins, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Code Analysis Agents leveraging Claude Code and needing remote GitHub repository operations Plugin marketplace for Claude Code

tenequm tenequm
[0]
[0]
Updated: 2/20/2026

Agent Capability Analysis

The gh-cli skill by tenequm is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Ideal for Code Analysis Agents leveraging Claude Code and needing remote GitHub repository operations

Core Value

Empowers agents to perform remote repository analysis, codebase comparison, and code discovery using GitHub CLI, enabling operations like fetching specific files, comparing codebases side-by-side, and searching code across GitHub, all without cloning repositories, utilizing APIs and jq for data parsing

Capabilities Granted for gh-cli

Analyzing repositories without cloning for efficient code review
Comparing codebases side-by-side for difference detection
Fetching specific files from any repository for targeted analysis
Discovering trending repositories and code patterns for market research

! Prerequisites & Limits

  • Requires GitHub CLI installation and configuration
  • Dependent on GitHub API availability and rate limits
  • Limited to repositories accessible via GitHub API
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

gh-cli

Install gh-cli, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

GitHub CLI - Remote Analysis & Discovery

Remote repository operations, codebase comparison, and code discovery without cloning.

When to Use

  • Analyze repositories without cloning
  • Compare codebases side-by-side
  • Fetch specific files from any repo
  • Find trending repositories and code patterns
  • Search code across GitHub

Quick Operations

Fetch a file remotely

bash
1gh api repos/OWNER/REPO/contents/path/file.ts | jq -r '.content' | base64 -d

Get directory listing

bash
1gh api repos/OWNER/REPO/contents/PATH

Search code

bash
1gh search code "pattern" --language=typescript
bash
1gh search repos --language=rust --sort stars --order desc

Compare Two Codebases

Systematic workflow for comparing repositories to identify similarities and differences.

Example use: "Compare solana-fm/explorer-kit and tenequm/solana-idls"

Step 1: Fetch directory structures

bash
1gh api repos/OWNER-A/REPO-A/contents/PATH > repo1.json 2gh api repos/OWNER-B/REPO-B/contents/PATH > repo2.json

If comparing a monorepo package, specify the path (e.g., packages/explorerkit-idls).

Step 2: Compare file lists

bash
1jq -r '.[].name' repo1.json > repo1-files.txt 2jq -r '.[].name' repo2.json > repo2-files.txt 3diff repo1-files.txt repo2-files.txt

Shows files unique to each repo and common files.

Step 3: Fetch key files for comparison

Compare package dependencies:

bash
1gh api repos/OWNER-A/REPO-A/contents/package.json | jq -r '.content' | base64 -d > repo1-pkg.json 2gh api repos/OWNER-B/REPO-B/contents/package.json | jq -r '.content' | base64 -d > repo2-pkg.json

Compare main entry points:

bash
1gh api repos/OWNER-A/REPO-A/contents/src/index.ts | jq -r '.content' | base64 -d > repo1-index.ts 2gh api repos/OWNER-B/REPO-B/contents/src/index.ts | jq -r '.content' | base64 -d > repo2-index.ts

Step 4: Analyze differences

Compare the fetched files to identify:

API Surface

  • What functions/classes are exported?
  • Are the APIs similar or completely different?

Dependencies

  • Shared dependencies (same approach)
  • Different dependencies (different implementation)

Unique Features

  • Features only in repo1
  • Features only in repo2

For detailed comparison strategies, see references/comparison.md.

bash
1# Most starred repos 2gh search repos --sort stars --order desc --limit 20 3 4# Trending in specific language 5gh search repos --language=rust --sort stars --order desc 6 7# Recently popular (created in last month) 8gh search repos "created:>2024-10-01" --sort stars --order desc 9 10# Trending in specific topic 11gh search repos "topic:machine-learning" --sort stars --order desc
bash
1# Find popular implementations 2gh search code "function useWallet" --language=typescript --sort indexed 3 4# Find code in popular repos only 5gh search code "implementation" "stars:>1000" 6 7# Search specific organization 8gh search code "authentication" --owner=anthropics

For complete discovery queries and patterns, see references/discovery.md.

Search Basics

bash
1# Search across all repositories 2gh search code "API endpoint" --language=python 3 4# Search in specific organization 5gh search code "auth" --owner=anthropics 6 7# Exclude results with negative qualifiers 8gh search issues -- "bug report -label:wontfix"
bash
1# Find open bugs 2gh search issues --label=bug --state=open 3 4# Search assigned issues 5gh search issues --assignee=@me --state=open

For advanced search syntax, see references/search.md.

Special Syntax

Field name inconsistencies

IMPORTANT: GitHub CLI uses inconsistent field names across commands:

Fieldgh repo viewgh search repos
StarsstargazerCountstargazersCount
ForksforkCountforksCount

Examples:

bash
1# ✅ Correct for gh repo view 2gh repo view owner/repo --json stargazerCount,forkCount 3 4# ✅ Correct for gh search repos 5gh search repos "query" --json stargazersCount,forksCount

Excluding search results

When using negative qualifiers (like -label:bug), use -- to prevent the hyphen from being interpreted as a flag:

bash
1gh search issues -- "query -label:bug"

For more syntax gotchas, see references/syntax.md.

Advanced Workflows

For detailed documentation on specific workflows:

Core Workflows:

GitHub Operations:

Setup & Configuration:

Resources

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is gh-cli?

Ideal for Code Analysis Agents leveraging Claude Code and needing remote GitHub repository operations Plugin marketplace for Claude Code

How do I install gh-cli?

Run the command: npx killer-skills add tenequm/claude-plugins. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for gh-cli?

Key use cases include: Analyzing repositories without cloning for efficient code review, Comparing codebases side-by-side for difference detection, Fetching specific files from any repository for targeted analysis, Discovering trending repositories and code patterns for market research.

Which IDEs are compatible with gh-cli?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for gh-cli?

Requires GitHub CLI installation and configuration. Dependent on GitHub API availability and rate limits. Limited to repositories accessible via GitHub API.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add tenequm/claude-plugins. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use gh-cli immediately in the current project.

Related Skills

Looking for an alternative to gh-cli or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI