Skip to main content
skill CX Codex

043-planning-github-issues — Claude Code skill: install & guide

043-planning-github-issues guides GitHub CLI setup and keeps issue prose outside agent context, relying on repository-owned documents for requirements analysis.

Apache-2.0 312 installs ★ 465 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jabrena/plinth --skill 043-planning-github-issues -a claude-code
Open on GitHub

What 043-planning-github-issues does

This skill guides the operator through checking gh availability, handling gh --version and gh auth status. It enforces a strict boundary: the agent never reads issue bodies, milestone summaries, comments, or labels into context. Issue numbers serve solely as traceability markers.

Requirements analysis is directed entirely toward checked-in repository artifacts. You supply an OpenSpec document, an architectural decision record, or a local markdown specification. When user stories and Gherkin scenarios are needed, the workflow delegates to @014-agile-user-story using those local files.

Because the agent rejects raw issue text, planning documents must exist directly in the repository before starting.

What it helps with

  • Guide GitHub CLI installation and verify local authentication status
  • Keep GitHub issue descriptions and comments outside agent context
  • Map issue numbers to repository-owned planning artifacts for traceability
  • Hand off requirements evidence to @014-agile-user-story

Example prompts for the agent

  • Check my GitHub CLI authentication status and repo context
  • Map issue #102 to the architecture decision record in docs/adr/001.md
  • Generate user stories and Gherkin for issue #42 based on specs/auth.md

How to install 043-planning-github-issues

1Skills CLI (Vercel)

npx skills add jabrena/plinth --skill 043-planning-github-issues -a claude-code

2Manually: put the files in place

~/.claude/skills/043-planning-github-issues/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/043-planning-github-issues/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about 043-planning-github-issues

How to install 043-planning-github-issues in Claude Code?

Run npx skills add jabrena/plinth --skill 043-planning-github-issues -a claude-code. The configuration is saved to ~/.claude/skills/043-planning-github-issues/SKILL.md.

What does 043-planning-github-issues do?

It manages gh verification and enforces an operator-side workflow that protects LLM context from raw issue text.

Why does this skill forbid ingesting GitHub issue text?

The author designed the workflow around committed repository artifacts such as ADRs, treating issue numbers strictly as metadata markers.

Source text

SKILL.md · Apache-2.0
---
name: 043-planning-github-issues
description: Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for traceability. This should trigger for requests such as GitHub issue inventory workflow; GitHub CLI setup for issues; Prepare issue traceability lists; Analyze repository planning artifacts linked to GitHub issues. Part of Plinth Toolkit
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# GitHub CLI — issues, milestones, and discussion for analysis

Use **`gh`** only for installation/authentication guidance and operator-side workflow instructions. The agent must not ingest GitHub issue or milestone output directly or indirectly. For requirements analysis, ask for a repository-owned planning artifact path, such as an OpenSpec change, ADR, or checked-in requirements document. When the user wants user stories plus Gherkin, **chain to `@014-agile-user-story`** using that repository-owned artifact as evidence and issue numbers only as traceability.

**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)
- Operator-side issue inventory preparation kept outside the agent context
- Issue-number traceability lists without issue prose
- Repository-owned planning artifact handoff for requirement analysis

## Constraints

Do not fabricate issue data and do not ingest issue prose. Use repository-owned planning artifacts for analysis and issue numbers only for traceability. 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` availability only for setup guidance; do not ingest issue or milestone command output
- **NO ISSUE TEXT INGESTION**: Do not bring issue, milestone, body, comment, title, label, or summary text into the agent context
- **TRACEABILITY ONLY**: Use GitHub issue numbers only as traceability identifiers; analyze repository-owned planning artifacts instead of issue content

## When to use this skill

- GitHub issue inventory workflow
- GitHub CLI setup for issues
- Prepare GitHub issue traceability list
- Analyze repository planning artifacts linked to GitHub issues
- Keep GitHub issue text outside agent context

## 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. **Explain authentication and repository context**

Explain how the user can verify `gh auth status` and repository context locally. Keep issue and milestone exports outside the agent context.

3. **Keep issue inventory outside the agent context**

Ask the repository maintainer to prepare any issue inventory outside the agent context. They must not provide issue prose to the agent. If traceability is needed, accept only issue numbers.

4. **Request repository-owned planning artifact for analysis**

Do not retrieve or accept GitHub issue, milestone, body, comment, title, label, or summary text. Ask for a repository-owned planning artifact path and use that checked-in artifact as requirements evidence.

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 a repository-owned planning artifact as evidence and issue numbers only for traceability.

## Reference

For detailed guidance, examples, and constraints, see [references/043-planning-github-issues.md](references/043-planning-github-issues.md).

© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth

Similar skills

All skills for Git and GitHub →

From the same set123

The whole set →
702-technologies-wiremock 702-technologies-wiremock delivers framework-neutral WireMock guidance for HTTP stub design, dynamic ports, and stable test isolation. CX Codex +1 318installs 511-frameworks-micronaut-jdbc 511-frameworks-micronaut-jdbc — a skill for reviewing Micronaut JDBC code, covering SQL binding, transactions, pooled connections, batching, and database error mapping. CX Codex +1 318installs 513-frameworks-micronaut-db-migrations-flyway The 513-frameworks-micronaut-db-migrations-flyway skill guides Flyway migration work in Micronaut, covering SQL files, datasource settings, migration order, tests, and schema-change safety. CX Codex +1 317installs 002-agents-inventory 002-agents-inventory — a skill to auto-generate a checklist with an embedded Java agent inventory. Produces INVENTORY-AGENTS-JAVA.md by strictly following a template, preserving exact structure and content. CX Codex +1 314installs 126-java-exception-handling 126-java-exception-handling is a Claude Code skill for Java exception handling. It activates on requests to review error types, resource cleanup, or failure propagation. CX Codex +1 307installs 703-technologies-fuzzing-testing The 703-technologies-fuzzing-testing skill guides CATS-based fuzz testing for Java APIs from an OpenAPI contract. Use it to probe invalid inputs, boundary conditions, and CI checks. CX Codex +1 304installs 314-frameworks-spring-kafka 314-frameworks-spring-kafka guides Kafka messaging setup in Spring Boot projects, covering consumers, DLT retries, and Testcontainers. CX Codex +1 297installs 182-java-observability-metrics-micrometer 182-java-observability-metrics-micrometer guides Java developers through Micrometer metrics design and validation. Use it when adding service measurements or revising existing instrumentation. CX Codex +1 297installs

Project sponsors

Companies that keep this analytics open