用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dannote/dot-pi --skill github-issues命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Prepare, publish, repair, or verify package releases and changelogs. Always use for package/version release, publish, ship, tag, changelog, release notes, registry publication, documentation publication, or GitHub Release work. Distinguish package releases from application deployments before acting.
Write or revise X/Twitter developer announcement threads in the user's preferred style. Use for technical launch threads, project announcements, release threads, and threads with code screenshots/snippets.
Use agent-browser CLI for website automation: navigate, click/fill, scrape, screenshot, test web apps, debug console/network.
基于 SOC 职业分类
正在显示 SKILL.md
| name | github-issues |
| description | Use gh CLI to view, triage, fix, link, create, or close GitHub Issues. |
Never pass multiline Markdown through --body "...". Shell quoting can leak literal \n into GitHub.
Always write Markdown to a temp file and use --body-file:
cat > /tmp/body.md <<'EOF'
## Summary
- ...
## Tests
- `...`
EOF
gh pr create --body-file /tmp/body.md
# or
gh pr edit <number> --body-file /tmp/body.md
# or
gh issue create --body-file /tmp/body.md
gh issue view <number>
For non-trivial bodies, always write the draft to a temp file first. Do not inline long Markdown with shell quoting.
cat > /tmp/issue.md <<'EOF'
### What happened?
...
EOF
gh issue create --repo OWNER/REPO --title "Short title" --body-file /tmp/issue.md
Before creating issues in someone else's repo, check templates/contributing docs and keep the report concise.
gh api repos/OWNER/REPO/contents/.github/ISSUE_TEMPLATE --jq '.[].name'
gh api repos/OWNER/REPO/contents/CONTRIBUTING.md --jq .content | base64 --decode
If gh issue create prompts for confirmation, review the preview carefully before accepting.
fix: description (#1) or fix: description (fixes #1) — auto-closes on merge to default branch([#1](https://github.com/owner/repo/issues/1))fixes #1 — does NOT auto-close, must close manuallyAlways thank the reporter and mention the fix version:
gh issue close <number> --comment "Fixed in v1.2.3. Thanks for the report!"
For npm packages, simulate fresh install:
npm pack --pack-destination /tmp/
cd /tmp && mkdir test && cd test
echo '{"name":"test"}' > package.json
bun add /tmp/package-name-1.0.0.tgz
./node_modules/.bin/command --help