github

Triage GitHub repositories, pull requests, and issues through the connected GitHub app.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill github-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/AarnavBaddam/skills/tree/main/github
Command: npx skills add https://github.com/AarnavBaddam/skills --skill github-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? It removes the guesswork from general GitHub work by orienting repository, pull request, and issue context first, then routing review follow-up, CI debugging, or publish tasks to the right specialist workflow. ## Core Features & Use Cases - Repository and PR Triage: Summarize recent pull requests, issues, patches, comments, labels, and reactions using structured data from the GitHub app connector. - Hybrid Connector and CLI Model: Prefer the GitHub app for PR and issue data while using local git and gh only for gaps like current-branch PR discovery, commits, pushes, and Actions log inspection. - Intelligent Routing: Classify requests into triage, review follow-up, CI debugging, or publish workflows and hand off to the matching specialist skill immediately. - Use Case: Ask for a summary of open PRs in a repository, and the skill gathers structured PR context, highlights what needs attention, and routes any failing-check investigation to the CI debugging workflow. ## Quick Start Use the github skill to summarize the open pull requests in this repository and tell me which ones need attention.

Frequently Asked Questions about github

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

FAQPage Schema
How do I summarize open pull requests in a GitHub repository?

Provide the repository identifier or work from a local checkout, and the skill gathers structured PR data through the GitHub app connector. It returns a concise summary of PR state, comments, labels, and the next likely action.

When should I use the GitHub connector versus the gh CLI?

Use the GitHub app connector for PR, issue, comment, label, and reaction data since it works without a local checkout. Use local git and gh only for current-branch PR discovery, branch creation, commits, pushes, auth status, and Actions log inspection.

Can this skill inspect GitHub Actions logs for failing checks?

GitHub Actions logs are not available through the connector alone. Failing check investigation and CI log inspection are routed to the gh-fix-ci specialist skill, which uses the gh CLI for that workflow.

What happens if the repository is not specified in the request?

The skill first tries to resolve the repository from the request or local git context, including current-branch PR discovery via gh. If the repository remains ambiguous, it asks for the repo identifier rather than guessing.

How are code review comments and requested changes handled?

Requests about unresolved review threads, requested changes, or inline review feedback are classified as review follow-up. The skill routes them immediately to the gh-address-comments specialist skill instead of handling them in general triage.