043-planning-github-issues
This Claude Code skill provides a command-line interface for querying GitHub issues and milestones using the `gh` CLI tool. It begins with an interactive installation check that stops to offer guidance if `gh` is missing, then verifies authentication, lists issues with optional milestone filtering rendered as markdown tables, loads full issue bodies and comment threads for analysis, and can chain to user story creation workflows. Use it when you need to retrieve, summarize, or analyze GitHub issue data programmatically.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/043-planning-github-issues && cp -r /tmp/043-planning-github-issues/skills/043-planning-github-issues ~/.claude/skills/043-planning-github-issuesSKILL.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) ## When to use this skill - gh issue list - List GitHub issues - Issues in milestone - GitHub CLI issues - gh issue view comments ## Workflow 1. **Run interactive install gate** Check `gh --version`; if missing, stop and ask whether the user wants installation guidance before any issue operations. 2. **Verify authentication and repository context** Confirm `gh auth status`, authenticate if needed, and establish target repository context via `--repo` or git remote. 3. **List issues and milestones** Retrieve issues (optionally by milestone/state) using `gh issue list --json` and present summaries as markdown pipe tables. 4. **Load full thread for analysis** Read issue body and all comments via `gh issue view --json` or `--comments`, then provide evidence-based analysis. 5. **Chain to user story workflow when requested** When user asks for user stories and Gherkin from issues, hand off to `@014-agile-user-story` using GitHub-sourced content. ## Reference For detailed guidance, examples, and constraints, see [references/043-planning-github-issues.md](references/043-planning-github-issues.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project