How do I install the 021 Tooling Github skill?

Run npx skillmds add majiayu000/021-tooling-github in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 021 Tooling Github safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 021 Tooling Github?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 021 Tooling Github free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 021 Tooling Github?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

021 Tooling Github by majiayu000 — Agent Skill

Name: 021 Tooling Github
Rating: 4.2 (5 reviews)
Author: majiayu000

021 Tooling Github

Use when you need the GitHub CLI (`gh`) to verify installation, list issues (all or by milestone) as markdown tables, fetch issue bodies and comments for analysis, or hand off to @014-agile-user-story when creating user stories from GitHub threads. Uses an interactive install gate — if `gh` is missing, ask whether to show installation guidance before any issue commands. Part of the skills-for-java project

majiayu000 77d5e93 2 files · 3.4 KB Updated Sep 9, 2026 567 repo stars

File contents

GitHub CLI — issues, milestones, and discussion for analysis

Use gh to work with GitHub issues: first run an interactive check—if gh is not installed, stop, ask whether the user wants installation guidance (see the consultative pattern in 112-java-maven-plugins, Maven Wrapper step), wait for an answer, then continue. When gh is available, confirm auth, list issues with optional milestone filters, render markdown tables from --json output, load full issue bodies and comment threads for analysis, and when the user wants user stories plus Gherkin, chain to @014-agile-user-story using issue content as source material for the interactive questionnaire.

What is covered in this Skill?

Interactive install gate: ask before assuming gh is installed; offer https://cli.github.com/ and OS hints when the user agrees
Install/auth checks (gh --version, gh auth status, gh auth login)
Repository context (--repo, inferred from git remote)
Issue lists: states, limits, milestone filter, gh issue list --json for tabular output
Milestone discovery via gh api when titles are unknown
Deep reads: gh issue view with --json (body, comments) or --comments

Constraints

Do not fabricate issue data; use only gh output (or explicitly agreed public REST API responses). Never print tokens or secrets.

INTERACTIVE GATE: If gh is missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listing
FIRST (after gate): Verify gh is available before issuing subcommands
TABLES: Prefer --json + markdown pipe tables for issue list summaries
THREAD: For analysis, include body and all comments (or explicitly summarize with omissions noted)
014: For user stories from issues, use @014-agile-user-story and align answers with GitHub-sourced text

When to use this skill

gh issue list
List GitHub issues
Issues in milestone
GitHub CLI issues
gh issue view comments

Reference

For detailed guidance, examples, and constraints, see references/021-tooling-github.md.

---name: 021-tooling-githubdescription: Use when you need the GitHub CLI (`gh`) to verify installation, list issues (all or by milestone) as markdown tables, fetch issue bodies and comments for analysis, or hand off to @014-agile-user-story when creating user stories from GitHub threads. Uses an interactive install gate — if `gh` is missing, ask whether to show installation guidance before any issue commands. Part of the skills-for-java projectlicense: Apache-2.0---# GitHub CLI — issues, milestones, and discussion for analysis Use **`gh`** to work with GitHub issues: **first** run an **interactive** check—if `gh` is not installed, **stop**, ask whether the user wants installation guidance (see the consultative pattern in **`112-java-maven-plugins`**, Maven Wrapper step), **wait** for an answer, then continue. When `gh` is available, confirm auth, list issues with optional milestone filters, render **markdown tables** from `--json` output, load **full issue bodies and comment threads** for analysis, and when the user wants user stories plus Gherkin, **chain to `@014-agile-user-story`** using issue content as source material for the interactive questionnaire. **What is covered in this Skill?** - **Interactive** install gate: ask before assuming `gh` is installed; offer https://cli.github.com/ and OS hints when the user agrees - Install/auth checks (`gh --version`, `gh auth status`, `gh auth login`) - Repository context (`--repo`, inferred from git remote) - Issue lists: states, limits, milestone filter, `gh issue list --json` for tabular output - Milestone discovery via `gh api` when titles are unknown - Deep reads: `gh issue view` with `--json` (body, comments) or `--comments` ## Constraints Do not fabricate issue data; use only `gh` output (or explicitly agreed public REST API responses). Never print tokens or secrets. - **INTERACTIVE GATE**: If `gh` is missing, **stop**, ask whether the user wants installation guidance, **wait**—do not skip to issue listing - **FIRST** (after gate): Verify `gh` is available before issuing subcommands - **TABLES**: Prefer `--json` + markdown pipe tables for issue list summaries - **THREAD**: For analysis, include body and all comments (or explicitly summarize with omissions noted) - **014**: For user stories from issues, use `@014-agile-user-story` and align answers with GitHub-sourced text ## When to use this skill - gh issue list - List GitHub issues - Issues in milestone - GitHub CLI issues - gh issue view comments ## Reference For detailed guidance, examples, and constraints, see [references/021-tooling-github.md](references/021-tooling-github.md).

Frequently asked questions