一键导入
gh-pr
Run simple GitHub PR operations in natural language: open PR, pull new comments idempotently, and mark one or many comments pending/addressed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Run simple GitHub PR operations in natural language: open PR, pull new comments idempotently, and mark one or many comments pending/addressed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Build a fast, actionable branch/PR/commit context pack with scope, intent, changed files, hotspots, risks, and next actions. Use before handing work to another agent, reviewing a branch, resuming unfamiliar work, or preparing a PR/code-review prompt.
Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.
User guide for the local squash-safe `stack` CLI for stacked PR repair. Use when someone asks how to inspect, track, sync, merge, repair, document, or undo stacked pull requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.
Manage long-running terminal jobs in a dedicated tmux-opencode session using wrapper scripts for run/wait, health checks, and crash-recovery cleanup.
Video understanding and transcription with intelligent multi-provider fallback. Use when: (1) Transcribing video or audio content, (2) Understanding video content including visual elements and scenes, (3) Analyzing YouTube videos by URL, (4) Extracting information from local video files, (5) Getting timestamps, summaries, or answering questions about video content. Automatically selects the best available provider based on configured API keys - prefers full video understanding (Gemini/OpenRouter) over ASR-only providers. Supports model selection per provider.
Designs and refactors React component APIs toward compound composition: fewer boolean mode props, clearer seams, context-backed internals, and JSX-first variant assembly. Use when building or reviewing React components with many props, conditional render branches, render props/slots, shared form/composer/card/table internals, or when the user mentions composition, compound components, Radix-style APIs, prop drilling, boolean props, or "composition is all you need".
| name | gh-pr |
| description | Run simple GitHub PR operations in natural language: open PR, pull new comments idempotently, and mark one or many comments pending/addressed. |
| references | ["scripts/README.md"] |
Use this skill for minimal, direct PR operations.
gh pr and asks to open PR, check new comments, or mark comments pending/addressed.ADDRESSED_REACTION=+1 (:thumbsup:) means addressed.PENDING_REACTION=eyes (:eyes:) means in progress.BOT_REPLY_PREFIX=🤖 marks bot-authored replies.Use native CLI and avoid over-automation:
gh pr create --title "<title>" --body-file <body.md> --base <base-branch>
Use helper script:
bun skills/gh-pr/scripts/gh_pr_ops.ts queue --repo <owner/repo> --pr <number>
This fetches issue comments, inline review comments, and top-level PR review bodies (including summary reviews from Cursor Bugbot, Hodor, and similar tools), then returns only unmarked, non-bot-prefixed items.
--status addressed now resolves GitHub review threads for PR review comments (instead of only adding a reaction).
Issue comments still use reactions.
# mark pending when you start work
bun skills/gh-pr/scripts/gh_pr_ops.ts mark --repo <owner/repo> --pr <number> --ids 12345 --status pending
# mark addressed when done
bun skills/gh-pr/scripts/gh_pr_ops.ts mark --repo <owner/repo> --pr <number> --ids 12345 --status addressed
# many
bun skills/gh-pr/scripts/gh_pr_ops.ts mark --repo <owner/repo> --pr <number> --ids 12345,12346,12347 --status addressed
When user says "address comment" (or equivalent), execute this full sequence:
pending (:eyes:).addressed (:+1:) only after push and only if actually resolved.If verification fails or the fix is incomplete, keep the comment in pending state and report what remains.
pending (:eyes:).addressed (:+1:) only if the comment is actually resolved.