菜单
Generate a weekly changelog card for Twitter/X. Reads git log, distills the work into 6 punchy items, fills an HTML template, and opens it in the browser ready to screenshot.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Wire PostHog analytics, Sentry error tracking, and a health endpoint into any web project. Reads your stack, installs the right packages, and instruments your app so you stop flying blind in production.
Full Answer Engine Optimization audit — make your project discoverable by AI search engines (ChatGPT, Perplexity, Claude, Google AI Overviews), not just Google. Use when the user wants to improve their site's visibility in AI-powered search, add structured data, create llms.txt, optimize for AI citations, or audit AEO readiness. Triggers on requests like "AEO audit", "AI search optimization", "make my site visible to AI", "structured data", "schema markup", "llms.txt", "answer engine", "AI discoverability", or any mention of being found by AI search engines or chatbots.
Audit or generate all UI microcopy for an app — empty states, error messages, loading states, onboarding flows, tooltips, button labels, confirmation dialogs, and success messages. Use when the user wants to write UI copy, fix empty states, improve error messages, audit UX writing, make their app feel polished, or replace placeholder text. Triggers on requests like "write app copy", "fix my empty states", "error messages", "UI copy", "microcopy", "UX writing", "my app feels robotic", "placeholder text", "button labels", "onboarding copy", "toast messages", or any mention of in-app text, UI writing, or product copy.
Write cold emails that actually get responses. Covers investors, employers, mentors, partners — anyone you don't know yet. Strict 2-4 sentence formula with real examples that got replies from Evan Spiegel, Mark Cuban, and Elon Musk. Triggers on requests like "cold email", "write an email to...", "reach out to...", "email this investor", "email this founder", "outreach email", "networking email", or any request to contact someone you don't have a relationship with yet.
Generate complete multi-touch cold outreach sequences — not just one email, but a full 3-5 email sequence with timing, escalation logic, and a different angle per touch. Use when the user needs a sales sequence, drip campaign, follow-up series, or any cold outreach with more than one touchpoint. Triggers on requests like "outreach sequence", "email sequence", "follow-up series", "drip campaign", "sales cadence", "multi-touch outreach", or when someone needs more than a single cold email.
Write a structured decision document when stuck between two or more approaches. Lays out options, tradeoffs, constraints, and picks one. Use when the user is debating architecture, choosing between tools, weighing tradeoffs, or stuck in analysis paralysis. Triggers on requests like "decision doc", "should I use X or Y", "help me decide", "which approach", "tradeoff analysis", "I'm stuck between", "pros and cons", "compare these options", "what should I pick", "architecture decision", or any request to choose between multiple approaches, tools, or implementations.
| name | changelog |
| description | Generate a weekly changelog card for Twitter/X. Reads git log, distills the work into 6 punchy items, fills an HTML template, and opens it in the browser ready to screenshot. |
| category | workflow |
| tags | ["changelog","twitter","marketing","git"] |
| author | tushaarmehtaa |
Generate the weekly changelog Twitter card. Run every Friday (or whenever you ship).
git log --oneline --since="7 days ago"
Get the stats:
# Commit count
git log --oneline --since="7 days ago" | wc -l
# Files + lines changed
git log --since="7 days ago" --pretty=tformat: --numstat | awk '{files++; add+=$1; del+=$2} END {print files " files · " add+del " lines"}'
Read each commit message. For any that are unclear, look at the diff:
git show [commit-hash] --stat
Group commits into themes. Ignore pure refactors, dependency bumps, and test fixes — users don't care. Focus on what changed for them.
Each item needs:
If fewer than 6 meaningful things shipped, combine small related items or include one "under the hood" item about stability/performance.
Look for a changelogs/ directory in the repo. If there's a template.html, use it.
If no template exists, create changelogs/template.html with this structure:
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<style>
* { margin: 0; padding: 0; box-sizing: border-box; }
body {
width: 1200px; height: 628px; overflow: hidden;
background: #09090b; font-family: 'JetBrains Mono', ui-monospace, monospace;
display: flex; flex-direction: column; padding: 48px;
}
.header { color: #71717a; font-size: 13px; margin-bottom: 32px; letter-spacing: 0.05em; }
.header span { color: #fafafa; }
.grid { display: grid; grid-template-columns: 1fr 1fr; gap: 20px; flex: 1; }
.item { display: flex; gap: 12px; }
.emoji { font-size: 18px; flex-shrink: 0; margin-top: 1px; }
.content h3 { color: #fafafa; font-size: 13px; font-weight: 700; margin-bottom: 4px; }
.content p { color: #71717a; font-size: 11px; line-height: 1.6; }
.content p strong { color: #a1a1aa; }
.footer { color: #3f3f46; font-size: 11px; margin-top: 24px; letter-spacing: 0.05em; }
</style>
</head>
<body>
<div class="header">what shipped this week · <span>MONTH DAY</span></div>
<div class="grid">
<div class="item"><div class="emoji">EMOJI</div><div class="content"><h3>TITLE</h3><p>BODY LINE 1<br>BODY LINE 2<br><strong>BODY LINE 3</strong></p></div></div>
<!-- repeat 5 more times -->
</div>
<div class="footer">N commits · N files · N lines · all live</div>
</body>
</html>
Create changelogs/YYYY-MM-DD.html (use today's date).
Fill in:
open changelogs/YYYY-MM-DD.html
Tell the user: "ready — screenshot the browser window (⌘+Shift+4 on Mac) and post it."
Lowercase. Direct. No buzzwords. User benefit first, technical detail never. If you can't explain the value to a non-engineer in one line, rewrite it.
If using an existing template — never touch the CSS. Content only. The design is locked.