043-planning-github-issues
强调不直接抓取原始 issue 的安全输入流程，适合需人工脱敏的场景。
可能要求安装 gh 并配置 GitHub 访问令牌，涉及凭据访问。
提供 gh 安装/认证指导并定义对清洗后 issue 的分析工作流。
指导 gh（GitHub CLI）的安装与认证，并教你把仓库的 issue 做成可分析的干净清单。适合需要对 issue 做汇总、分析或交接给产品/开发时用。特别在于不直接抓取原始敏感讨论，而是让你提供脱敏后的摘要，便于生成 user stories 或 Gherkin。
▸ 展开 SKILL.md 英文原文
Use when you need GitHub CLI (`gh`) installation/authentication guidance and a sanitized GitHub issue inventory workflow. The agent does not ingest GitHub issue or milestone output directly; it asks the user for sanitized issue summaries before analysis or @014-agile-user-story handoff. This should trigger for requests such as GitHub issue summary workflow; GitHub CLI setup for issues; Prepare sanitized GitHub issue inventory; Analyze GitHub issues with gh CLI; Summarize milestones and issue discussions safely. Part of Plinth Toolkit
帮我安装这个 skill：https://raw.githubusercontent.com/jabrena/plinth/main/skills/043-planning-github-issues/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/jabrena/plinth/main/skills/043-planning-github-issues/SKILL.md"# GitHub CLI — issues, milestones, and discussion for analysis Use **`gh`** only for installation/authentication guidance. The agent must not ingest GitHub issue or milestone output directly. For requirements analysis, ask the user to provide a sanitized issue inventory or summary in their own words. When the user wants user stories plus Gherkin, **chain to `@014-agile-user-story`** using sanitized issue context 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`,