github

Triage GitHub repositories, pull requests, and issues with connector and git fallbacks.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill github-dallay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/github
Command: npx skills add https://github.com/dallay/opencode-docker --skill github-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide fast orientation and decisive triage for GitHub repositories, pull requests, and issues so users can quickly understand state and next actions without manual inspection.

Core Features & Use Cases

  • Repository and PR orientation: Summarizes repository state, open PRs, issues, labels, and recent activity.
  • Hybrid connector-first workflows: Prefer the configured GitHub integration for structured data and fall back to local git and gh for branch discovery, commits, pushes, and Actions logs.
  • Routing to specialists: Classifies requests (triage, review follow-up, CI debugging, publish changes) and routes work to more specific skills when needed.
  • Use Case: Summarize the current branch's open PR, inspect patch changes and comments, then recommend whether to request changes, run CI diagnostics, or open a draft PR.

Quick Start

Ask the GitHub skill to summarize open pull requests in this repository and recommend the top actions to resolve them.

Frequently Asked Questions about github

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

FAQPage Schema
How do I triage open pull requests and issues in a GitHub repository?

Triage GitHub pull requests and issues using a configured connector with local gh fallbacks to summarize repository state, labels, comments, and recent activity, then recommending actionable next steps.

Can I get a summary of repository context and recent activity without manual inspection?

Yes, you can get repository context summaries by requesting orientation, which aggregates open pull requests, issues, and recent activity into concise actionable insights without manual inspection.

Does this GitHub triage workflow require a specific connector or can it use local git?

This GitHub triage workflow prefers a configured GitHub connector for structured data but applies local git and gh fallbacks for branch resolution, pull request discovery, and Actions log inspection.

What is the best way to debug CI failures from GitHub Actions logs?

The best way to debug CI failures is to route requests through CI debugging classification, which inspects local Actions logs to provide concise context and decisive next steps for resolution.

How do I decide whether to request changes, run diagnostics, or open a draft PR?

To decide whether to request changes, run CI diagnostics, or open a draft PR, the skill inspects patch changes and comments on the current branch's open pull request to recommend next actions.

When should I not use this approach for handling GitHub issues and pull requests?

You should not use this approach for handling GitHub issues and pull requests when you lack a configured GitHub connector and local git or gh CLI fallbacks, as hybrid workflows require them for branch discovery and Actions log inspection.