// Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI. Use when the user wants repository facts from GitHub without opening the browser, especially for PR status, CI failures, issue lists, or structured JSON output.
Use when the user asks Codex to research, find learning materials, process "素材：" links, "精读" a material, build a material radar, or use SenSight-like broad information retrieval for career learning and Agent infra tracking.
Track and synthesize current AI hotspots into a bilingual HTML daily report. Use when the user says "AI热点", asks for AI日报/AI日报 HTML/AI hot topics, or wants the best recent AI products, papers, viewpoints, and cognition-shifting items from AI/news aggregators.
Extract a Markdown heading tree with line numbers before editing or integrating notes. Use when you need to inspect a long Markdown file quickly and choose the best insertion point instead of editing blind.
Fetch and extract full text from arxiv paper HTML pages. Invoke when user asks to read an arxiv paper, analyze a paper's content, or when given an arxiv ID/URL.
Organize tasting menus, menu photos, and visit notes into the right gourmet note. Use when the user shares a restaurant menu, wants a tasting write-up, or asks to merge a new visit into Notes/Gourmet.md without overwriting earlier visits.
Browser automation. When you need to visit a webpage, open a website, take a screenshot, or perform browser automation, **you MUST read this SKILL.md first** — contains required parameters and operating procedures. **Calling the browser tool without reading may result in failed operations or unexpected behavior.**
| name | github-gh-cli |
| description | Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI. Use when the user wants repository facts from GitHub without opening the browser, especially for PR status, CI failures, issue lists, or structured JSON output. |
Use this skill when the task is about GitHub data and gh is the fastest path:
gh over browser navigation when command-line access is enough.--json and --jq when you need structured results.--repo owner/repo explicitly.gh auth login; do not attempt interactive credential setup yourself.gh pr view 123 --repo owner/repo
gh pr checks 123 --repo owner/repo
gh pr list --repo owner/repo --limit 20
gh run list --repo owner/repo --limit 10
gh run view <run-id> --repo owner/repo
gh run view <run-id> --repo owner/repo --log-failed
gh issue list --repo owner/repo --limit 20
gh issue list --repo owner/repo --json number,title,state --jq '.[]'
gh api repos/owner/repo/pulls/123
gh api repos/owner/repo/issues --jq '.[].title'