021 Tooling Github
Apps & Automation021-tooling-github021 Tooling Github is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/integration/021-tooling-github/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/021-tooling-github, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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
ghis 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 --jsonfor tabular output - Milestone discovery via
gh apiwhen titles are unknown - Deep reads:
gh issue viewwith--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
ghis missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listing - FIRST (after gate): Verify
ghis 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-storyand 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.