Development

021-tooling-github - Claude MCP Skill

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

SEO Guide: Enhance your AI agent with the 021-tooling-github tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to use when you need the github cli (`gh`) to verify installation, list issues (all or by milestone) as... Download and configure this skill to unlock new capabilities for your AI workflow.

🌟3 stars • 61 forks

📥0 downloads

API REST

View on GitHub🔗 Claude Servers

Documentation

SKILL.md

# 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).

Signals

Avg rating⭐ 0.0

Reviews0

Favorites0

Information

Repository: jabrena/cursor-rules-java
Author: jabrena
Last Sync: 4/8/2026
Repo Updated: 4/8/2026
Created: 4/5/2026

Reviews (0)

No reviews yet. Be the first to review this skill!

Related Skills

cursorrules

CrewAI Development Rules

⭐ 43932Has guide

README

Agents — Working Implementations

⭐ 37462

cn-check

Install and run the Continue CLI (`cn`) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.

⭐ 35767

firecrawl-build-search

Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

⭐ 35092