github

Extract and analyze GitHub data using the GitHub CLI.

2|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Thomascountz/claude_skills --skill github-thomascountz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/Thomascountz/claude_skills/tree/main/github
Command: npx skills add https://github.com/Thomascountz/claude_skills --skill github-thomascountz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you retrieve and analyze GitHub data without manual digging, enabling quick access to PRs, issues, runs, releases, and repository information for insights and automation.

Core Features & Use Cases

  • View repository details: Read repository metadata, languages, stargazers, and more
  • PR and issue analysis: List, view, and analyze PRs and issues for trends and metrics
  • Workflow & run insights: Inspect GitHub Actions runs, artifact data, and status
  • Code search & analytics: Query code across repos and perform complex data extraction (GraphQL examples)
  • Use Case: Generate a snapshot of recent activity and key metrics for a project board

Quick Start

Example: gh repo view owner/repo --json stargazers_count,open_issues_count

Frequently Asked Questions about github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract and analyze GitHub repository data using the command line?

Use the GitHub CLI (gh) to extract repository data like PR counts, issue metrics, and workflow status. The gh tool queries repositories and outputs JSON for analysis, enabling quick access to project metrics without manual inspection or API calls.

Can I query GitHub pull requests and issues to find trends or patterns?

Yes. The GitHub CLI lists and filters PRs and issues by status, author, date, and labels. Pipe results to jq or Unix tools to extract metrics, identify trends, and generate analytics summaries across individual or multiple repositories.

What's the best way to retrieve GitHub Actions workflow and run data?

The GitHub CLI inspects workflow runs, logs, and artifacts directly from the terminal. Query run status, execution time, and failure logs in JSON format, then process with standard Unix tools for dashboards, alerts, or performance analysis.

Does the GitHub CLI support cross-repository code search and analysis?

Yes. The gh CLI performs code search across multiple repositories and supports GraphQL queries for complex data extraction. Results export as JSON for downstream pattern matching, inventory audits, or compliance scanning.

Do I need authentication to retrieve private repository data with gh?

Yes. The GitHub CLI requires authentication via token or login. Once authenticated, you can read private repository metadata, PRs, issues, and workflows with the same commands used for public repositories.

What are the limits of using gh for GitHub data analysis versus the API directly?

The gh CLI is optimized for read-only queries and structured output. It wraps the GitHub API but focuses on common retrieval tasks. For custom GraphQL mutations, webhooks, or real-time streaming, direct API calls may be necessary.