AGENT SKILL

github

Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.

License 许可
MIT
最近更新
2026-07-19
Stars
★ 1
Forks
1

01 前言 Front Matter

name
github
description
Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.

02 资源文件 3

03 SKILL.md 正文

GitHub

Overview

Use this skill as the umbrella entrypoint for general GitHub work in this plugin. It should decide whether the task stays in repo and PR triage or should be handed off to a more specific review, CI, or publish workflow.

This plugin is intentionally hybrid:

  • Prefer the GitHub app from this plugin for repository, issue, pull request, comment, label, reaction, and PR creation workflows.
  • Use local git and gh only when the connector does not cover the job well, especially for current-branch PR discovery, branch creation, commit and push, gh auth status, and GitHub Actions log inspection.
  • Keep connector state and local checkout context aligned. If the request is about the current branch, resolve the local repo and branch before acting.

Once the intent is clear, route to the specialist skill immediately and do not keep broad GitHub triage in scope longer than needed.

Connector-First Responsibilities

Handle these directly in this skill when the request does not need a narrower specialist workflow:

  • repository orientation once the repo, PR, issue, or local checkout is identified
  • recent PR or issue triage
  • PR metadata summaries
  • PR patch inspection
  • PR comments, labels, and reactions
  • issue lookup and summarization
  • PR creation after a branch is already pushed

Prefer the GitHub app from this plugin for those flows because it provides structured PR, issue, and review-adjacent data without depending on a local checkout. If the repository is not already identifiable from the user request or local git context, ask for the repo instead of pretending there is a repo-search flow that may not exist.

Routing Rules

  1. Resolve the operating context first:
    • If the user provides a repository, PR number, issue number, or URL, use that.
    • If the request is about "this branch" or "the current PR", resolve local git context and use gh only as needed to discover the branch PR.
    • If the repository is still ambiguous after local inspection, ask for the repo identifier.
  2. Classify the request before taking action:
    • repo or PR triage: summarize PRs, issues, patches, comments, labels, reactions, or repository state
    • review follow-up: unresolved review threads, requested changes, or inline review feedback
    • CI debugging: failing checks, Actions logs, or CI root-cause analysis
    • publish changes: create or switch branches, stage changes, commit, push, and open a draft PR
  3. Route to the specialist skill as soon as the category is clear:
    • Review comments and requested changes: ../gh-address-comments/SKILL.md
    • Failing GitHub Actions checks: ../gh-fix-ci/SKILL.md
    • Commit, push, and open PR: ../yeet/SKILL.md
  4. Keep the hybrid model consistent after routing:
    • connector first for PR and issue data
    • local git and gh only for the specific gaps the connector does not cover

Default Workflow

  1. Resolve repository and item scope.
  2. Gather structured PR or issue context through the GitHub app from this plugin.
  3. Decide whether the task stays in connector-backed triage or needs a specialist skill.
  4. Route immediately when the work becomes review follow-up, CI debugging, or publish workflow.
  5. End with a clear summary of what was inspected, what changed, and what remains.

Output Expectations

  • For triage requests, return a concise summary of the repository, PR, or issue state and the next likely action.
  • For mixed requests, tell the user which specialist path you are taking and why.
  • For connector-backed write actions, restate the exact PR, issue, label, or reaction target before applying the change.
  • Never imply that GitHub Actions logs are available through the connector alone. That remains a gh workflow.

Examples

  • "Use GitHub to summarize the open PRs in this repo and tell me what needs attention."
  • "Help with this PR."
  • "Review the latest comments on PR 482 and tell me what is actionable."
  • "Debug the failing checks on this branch."
  • "Commit these changes, push them, and open a draft PR."

04 同仓库更多 Skills

zfifteen
zfifteen/skills-catalog

Zotero

Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.

★ 1
zfifteen
zfifteen/skills-catalog

zoom-apps-sdk

Use when using Apps SDK.

★ 1
zfifteen
zfifteen/skills-catalog

youtube

Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".

★ 1
zfifteen
zfifteen/skills-catalog

yeet

Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.

★ 1
zfifteen
zfifteen/skills-catalog

x-post-creator

Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.

★ 1
zfifteen
zfifteen/skills-catalog

x-api

Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".

★ 1