菜单
Pick a pending issue from docs/issues/draft/, show it for review, then publish to GitHub on confirmation
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/epicollect5/epicollect5-mobile-app --skill publish-issue命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | publish-issue |
| description | Pick a pending issue from docs/issues/draft/, show it for review, then publish to GitHub on confirmation |
Publish a previously-drafted issue body to a GitHub repository using the gh CLI.
Follow the Issue Publish Workflow defined in docs/workflows/publish-issue.md.
epicollect5/epicollect5-development-plan — the issues tracker is always this repo. Pass repo:<owner/name> to override.
docs/issues/draft/ — /publish-issue lists every *.md file in this directory and asks the user to pick one. After a successful publish, the file is removed.
This command is side-effecting (creates a public GitHub issue). The workflow always shows the user the resolved title, repo, and labels, and asks for explicit confirmation before running gh issue create. Confirmation may be skipped only when the user explicitly supplies the yes argument.
The user can pass arguments to override the interactive picker:
/publish-issue (no args) — list pending drafts and ask which to publish./publish-issue <file> — skip the picker, use the file directly (foo.md relative to docs/issues/draft/, docs/issues/draft/foo.md, or absolute)./publish-issue <file> repo:<owner/name> — publish to a specific repo instead of the default./publish-issue <file> title:<text> — override the title (otherwise extracted from the first H1)./publish-issue <file> labels:<csv> — apply labels (comma-separated)./publish-issue <file> yes — skip the confirmation prompt. Use only when the user explicitly opts out.Multiple overrides can be combined.