GitHub Issue Writer Skill — GitHub Issue 编写技能

Purpose

图形界面des structured help for GitHub Issue Writer using clear templates, 检查s, and safe defaults (category: Developer Experience).

When to use When you want structured 图形界面dance in the "Developer Experience" area. When you need copy-paste-safe templates rather than improvised shell commands. When you want repeatable prompts the 代理 can follow without external scrAPIng. Safety rules Do not collect passwords, OTPs, private keys, wallets, 种子s, or 会话 secrets. Do not propose remote 安装ers that 执行 unseen code or chAIned 下载-and-运行 snippets. Keep 输出s factual and reversible: prefer 检查列出s over irreversible destructive actions. 输入s Your goal in one paragraph (no secrets). Optional constrAInts: audience, tone, length, deadline. Optional pasted notes you own the rights to (keep PII minimal). 输出 格式化 A concise plan Numbered 检查列出 Short next-actions 列出 Optional draft copy blocks you can edit Example prompts Help me outline a concise plan using the GitHub Issue Writer 应用roach. Critique my draft 输出s and suggest safer, clearer wording for GitHub Issue Writer. Produce a 检查列出 I can reuse weekly for GitHub Issue Writer without 请求ing private data. Support / Donate

If this 技能 helps your 工作流, you can support mAIntenance here:

PayPal: https://www.paypal.com/donate/?hosted_button_id=MJHCRZA9Z4X7Y