Menu
Use gh CLI to view, triage, fix, link, create, or close GitHub Issues.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
AppleScript and JXA automation for macOS. Use when user asks to automate apps, control system, run AppleScript/osascript, or integrate with macOS applications.
X/Twitter CLI for posting tweets, reading threads, searching, and fetching news. Use when user asks to tweet, reply, read tweets, search X/Twitter, get mentions, view bookmarks, likes, followers, following, user timelines, or fetch trending news/topics.
Decode garbled Russian/English wrong-keyboard-layout text (ЙЦУКЕН/QWERTY).
Analyze a user's pi coding-agent session history for recurring behavior, prompting habits, workflow loops, friction, and preferences. Use when the user asks to inspect or reflect on pi sessions, common behavior patterns, agent/user interaction style, prompting habits, or personal pi workflow quality.
| 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