github

Triages GitHub repositories, pull requests, and issues through a connected GitHub app.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill github-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/plugins/cache/openai-curated/github/27651a43bf55185d924f7a1fc49043a0a8be65a0/skills/github
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill github-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? It removes the guesswork of handling general GitHub requests by orienting repository, pull request, and issue context first, then routing work to the correct specialist workflow for reviews, CI debugging, or publishing changes. ## Core Features & Use Cases - Repository and PR Triage: Summarize recent PRs, issues, patches, comments, labels, and reactions using structured data from the connected GitHub app. - Hybrid Connector Model: Prefer the GitHub app for PR and issue data while falling back to local git and gh for branch discovery, pushes, and Actions log inspection. - Specialist Routing: Hand off review follow-ups, failing CI checks, and commit-push-PR flows to dedicated skills once the request category is clear. - Use Case: Ask for a summary of open PRs in a repository; the skill gathers PR metadata through the connector, flags 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 URL, and the skill gathers structured PR metadata through the connected GitHub app. It returns a concise summary of PR state, comments, and labels along with the next likely action.

When should I use the GitHub connector versus local git and gh?▼

Use the GitHub app connector for repository, issue, PR, comment, label, and reaction data since it works without a local checkout. Use local git and gh for current-branch PR discovery, branch creation, commit and push, and GitHub 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 is routed to the gh-fix-ci specialist skill, which uses the gh CLI for Actions log inspection and CI root-cause analysis.

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

The skill first tries to resolve context from local git state, such as the current branch and its associated PR. If the repository remains ambiguous after local inspection, it asks for the repo identifier rather than guessing.

How are 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.