x-announcement

<quick_start> <automation_workflow> One release, one announcement - fully automated:

1. Generate post: Extract highlights from CHANGELOG for version
2. User confirmation: Show preview, allow editing, get approval
3. Post to X: Send via API (http://5.161.75.135:8080)
4. Poll for tweet ID: Wait until post is live
5. Reply with link: Post GitHub release URL as threaded reply
6. Display URLs: Show both tweet links for verification

Example flow:

Generating X announcement for v2.7.0...

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
X Announcement Preview
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Spec-Flow v2.7.0 is here!

- One-command releases with CI validation
- Auto-close GitHub issues when features ship
- Essential cleanup for all deployment models

Ship features faster with less manual work.

Characters: 187/280
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Options:
1. Post as-is
2. Edit post text
3. Skip X announcement

Posting to X... (ID: 12345)
Waiting for publish... (3s)
Posted to X!

Posting GitHub link as threaded reply... (ID: 12346)
GitHub link posted!

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
X Announcement Posted!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Main Post:
   https://x.com/username/status/1234567890

GitHub Link Reply:
   https://x.com/username/status/1234567891

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

</automation_workflow>

<trigger_conditions> Auto-invoke when:

• /release command completes successfully
• Manual invocation for any release
• User mentions "announce release", "post to X", "tweet release"

Context available:

• NEW_VERSION - Version number (e.g., "2.7.0")
• CHANGELOG.md - Release notes for extraction
• README.md - Feature highlights
• COMMIT_SHA - Git commit hash </trigger_conditions>

<post_generation_guidelines> Format requirements:

• Include version number prominently
• Highlight 1-3 key features/improvements
• Keep under 280 characters (leave room for editing)
• Use engaging language (not just bullet points)
• End with call-to-action or benefit statement
• Do NOT use emojis (UTF-8 encoding issues with X API)

Content extraction:

1. Read CHANGELOG.md → Extract ## [NEW_VERSION] section
2. Identify top features: Prioritize Added > Fixed > Changed
3. Format with engaging tone (no emojis)
4. Validate character count (≤280)

See references/post-templates.md for examples and guidelines. </post_generation_guidelines> </quick_start>

Extract release highlights:

# Read CHANGELOG section for version
SECTION=$(sed -n "/## \[${NEW_VERSION}\]/,/## \[/p" CHANGELOG.md | head -n -1)

# Extract Added features
ADDED=$(echo "$SECTION" | grep -A 10 "### Added" | grep "^-" | head -3)

# Extract Fixed items
FIXED=$(echo "$SECTION" | grep -A 10 "### Fixed" | grep "^-" | head -2)

# Format into engaging post
# Template: 🚀 Spec-Flow v${NEW_VERSION} is here!
# ${FEATURE_EMOJI} ${FEATURE_1}
# ${FEATURE_EMOJI} ${FEATURE_2}
# ${BENEFIT_STATEMENT}

Display preview with character count for user review. </step_1_generate>

<step_2_confirm> 2. Get User Confirmation

Use AskUserQuestion or direct prompt:

Options:
1. ✅ Post as-is
2. ✏️  Edit post text
3. ❌ Skip X announcement

If user selects Edit:

• Prompt for new text
• Validate ≤280 characters
• Show updated preview
• Ask for confirmation again

If user selects Skip:

• Exit gracefully
• Continue with release summary </step_2_confirm>

<step_3_post> 3. Post to X API

Send POST request with confirmed content:

# Write content to temp file for proper UTF-8 encoding
cat > /tmp/x-post.txt << 'EOF'
<user-confirmed text>
EOF
POST_CONTENT=$(cat /tmp/x-post.txt | jq -Rs .)

RESPONSE=$(curl -s -X POST "http://5.161.75.135:8080/api/v1/posts/" \
  -H "Content-Type: application/json" \
  -d "{\"content\": $POST_CONTENT, \"scheduled_at\": null}")

POST_ID=$(echo "$RESPONSE" | jq -r '.id')

echo "📤 Posting to X... (ID: $POST_ID)"