菜单
Turn a Slack feature thread into researched, tested, reviewed behavior in a GitHub pull request and report the result back in the thread. Use when Slack requests net-new or intentionally changed behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Extract speaker-labelled transcripts and exact video frames from Fathom share URLs. Use when asked to read, summarize, review, or capture screenshots from a Fathom recording.
Extract timestamped transcripts and optional frames from accessible Loom share URLs. Use when a user asks to read, summarize, review, or capture screenshots from a Loom recording.
Bug-to-PR workflow. Use when existing or promised behavior produces the wrong result; route presentation-only corrections directly and substantial bugs through a regression test, evidence-backed implementation, adversarial review, and a GitHub pull request.
Feature-to-PR workflow. Use when a request adds net-new or intentionally changed behavior; route presentation-only changes directly and substantial work through researched tracer bullets, behavioral validation, adversarial review, and a GitHub pull request.
Turn a Slack bug thread into a diagnosed, tested, reviewed GitHub pull request and report the result back in the thread. Use when Slack reports existing or promised behavior producing the wrong result.
Provide reusable repository intake, evidence, review-remediation, pull-request, and response gates. Use when another skill needs to turn a request into a ready-for-review GitHub pull request.
| name | slack-feature-to-pr |
| description | Turn a Slack feature thread into researched, tested, reviewed behavior in a GitHub pull request and report the result back in the thread. Use when Slack requests net-new or intentionally changed behavior. |
| argument-hint | [Slack URL] |
/slack-to-pr intake gate with the supplied Slack permalink./feature-to-pr with the resulting brief as its complete request context. This workflow owns completion, so receive the pull-request URL and evidence back from it./slack-to-pr thread-update gate with the pull-request URL and a concise plain-language summary of the behavior added or changed./slack-to-pr preview and final-response gates.If feature classification routes to /bug-to-pr, retain this Slack lifecycle and use the bug explanations required by /slack-bug-to-pr in the thread update.
If any step exits without a pull-request URL, run the /slack-to-pr blocked-exit gate before responding.
Complete when: the ready-for-review PR and Slack lifecycle are complete and the final line is the exact GitHub pull-request URL.