dev-announce
dev-announce
Generate developer tool feature announcement tweets that are understated, proof-driven, and technically credible. Inspired by the style used in Bun's feature announcements.
Workflow
Copy this checklist and check off each step:
- [ ] Step 1: Understand the feature (read code/PR/commits if available)
- [ ] Step 2: Classify the feature type
- [ ] Step 3: Gather input details
- [ ] Step 4: Draft main tweet
- [ ] Step 5: Draft thread replies (optional)
- [ ] Step 6: Suggest visual proof
- [ ] Step 7: Verify against anti-patterns
Step 1: Understand the Feature
More from hyf0/skills
optimize-skill
Analyzes and optimizes an existing agent skill for conciseness, discoverability, and adherence to best practices. Use when a skill needs improvement, is too verbose, has poor activation rates, or fails to follow progressive disclosure patterns. Do NOT use for creating a new skill from scratch — use create-skill instead.
18code
Open the current working directory or a specified folder in Visual Studio Code.
11create-skill
Creates a new agent skill following best practices for structure, description writing, and progressive disclosure. Use when the user wants to author a new SKILL.md, scaffold a skill directory, or build a reusable skill. Do NOT use for improving an existing skill — use optimize-skill instead.
9resolve-pr-comments
Review and resolve GitHub PR review comments. Use when the user wants to address, fix, or resolve unresolved review comments on a pull request. TRIGGER when: user says \"resolve PR comments\", \"fix PR comments\", \"address review comments\", \"handle PR feedback\", or provides a PR URL with instructions about unresolved comments. Do NOT use for: creating PRs, reviewing code yourself, or general PR operations that don't involve resolving existing review comments.
4