菜单
Draft an algorithm-optimized tweet thread announcing the latest release.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Stage unstaged changes into one or more atomic git commits with project-compliant commit messages
Stage unstaged working tree changes into one or more atomic commits with git-stage-batch. Use when the user wants Codex to split unstaged edits into a clean commit series with project-compliant commit messages. Do not use for already-staged changes or for generic git help.
Decompose unstaged working-tree changes into narrow concerns, peel them into git-stage-batch batches, rebuild as a fine-grained atomic commit series, or polish an already-built series
Decompose unstaged working-tree changes into a clean commit series by identifying narrow product, workflow, or architectural concerns, peeling them into git-stage-batch batches, rebuilding atomic commits, or polishing an already-built series.
Commit the current staged index as one project-compliant git commit. Use when the user has already staged the exact changes they want to commit and wants help inspecting that staged set, drafting a compliant message, and creating the commit. Do not use for splitting or staging unstaged changes.
Commit the current staged index as one project-compliant git commit. Use when the user has already staged the exact changes they want to commit and wants help inspecting that staged set, drafting a compliant message, and creating the commit. Do not use for splitting or staging unstaged changes.
| name | release-tweet-thread |
| description | Draft an algorithm-optimized tweet thread announcing the latest release. |
| whenToUse | Use this when the user wants to announce a release on X/Twitter or draft social media posts about a release. |
| allowed-tools | Bash(git *), Bash(gh *), Read |
| user-invocable | true |
Your task is to draft a tweet thread announcing the latest release of this project, optimized for the X recommendation algorithm's ranking signals.
git describe --tags --abbrev=0.gh release view <tag>.<previous-tag>..<latest-tag> for detail.Write 2-4 tweets. Each tweet must be under 280 characters.
Tweet 1 (hook): Lead with a concrete before/after or a surprising result — something that makes people stop scrolling (dwell time is a ranking signal). Mention the project name and version. Include a link to the GitHub release page.
Tweet 2-3 (highlights): One highlight per tweet. Keep them concrete — what can users do now that they could not before? Avoid jargon. Use short sentences. Where possible, suggest including a short demo video or screenshot — media activates dedicated ranking signals (video quality views, photo expand) that plain text does not.
Final tweet (engagement close): End with a genuine question that invites replies — reply probability is one of the highest-weighted ranking signals. Good patterns: ask what feature users want next, ask about their current workflow pain point, or pose a "how do you handle X?" question. Pair with a low-friction call to action (install command, link to docs).
Present each tweet in a clearly numbered, copy-paste-ready block. Use a visual separator between tweets. Example:
--- Tweet 1 ---
<tweet text>
--- Tweet 2 ---
<tweet text>
After the thread, show the character count for each tweet so the user can verify they fit.
If any tweet would benefit from an attached image or video, note that below the thread with a brief description of what to capture (e.g., "Attach: 15-second terminal recording of the new --hierarchical flag").