043-planning-github-issues

Solid

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. This should trigger for requests such as gh issue list; List GitHub issues; Issues in milestone; GitHub CLI issues; gh issue view comments. Part of cursor-rules-java project

AI & Automation 404 stars 80 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 93/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# 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**—...