From bitwize-music
Reviews and polishes social media copy in album promo/ Markdown files for platforms like Twitter and Instagram. Checks character limits, iterates interactively before release.
npx claudepluginhub bitwize-music-studio/claude-ai-music-skills --plugin bitwize-musicThis skill is limited to using the following tools:
Interactive review and polish of social media copy in album `promo/` files. Walk through each post, approve or revise, and write polished results back to the file.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Interactive review and polish of social media copy in album promo/ files. Walk through each post, approve or revise, and write polished results back to the file.
After promo templates are populated with platform-specific copy, this skill provides structured review before release. Each post is presented with character counts, hashtag counts, and platform limit compliance. The user chooses actions (approve, revise, shorten, punch up, etc.) and polished copy is written back.
/bitwize-music:promo-writer generates initial copyPromo Videos (optional) → [Promo Writer] (or manual) → **[Promo Review]** → Release
Between populating promo templates and release-director.
Resolve the album from arguments:
Use MCP find_album with the album name from $ARGUMENTS. If no album specified, check get_session for last album context.
Locate promo directory:
{content_root}/artists/{artist}/albums/{genre}/{album}/promo/
Check which promo files exist and have content:
Glob for promo/*.md in the album directory. For each file, check if it contains populated content (not just template placeholders). A file is "populated" if it contains text beyond the template markers — look for content inside code blocks that isn't [placeholder text].
Report status:
## Promo Copy Status
| Platform | File | Status |
|----------|------|--------|
| Campaign | campaign.md | Populated |
| Twitter/X | twitter.md | Populated |
| Instagram | instagram.md | Template only |
| TikTok | tiktok.md | Not found |
| Facebook | facebook.md | Populated |
| YouTube | youtube.md | Template only |
3 of 6 platforms have copy ready for review.
If no promo files are populated:
No promo copy found to review.
Options:
1. Generate promo copy: /bitwize-music:promo-writer <album-name>
2. Populate promo templates manually (fill in promo/ files)
3. Skip promo review and proceed to release
If platform specified in arguments, review only that platform.
Otherwise, ask:
Which platforms to review?
[A] All populated platforms (campaign, twitter, facebook)
[1] Campaign strategy
[2] Twitter/X posts
[3] Facebook posts
List only populated platforms as numbered options.
For each selected platform file:
## and ### headings delineate sectionsFor each reviewable section, present the post with context:
## Twitter/X — Track 01: Track Title
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Track one tells the story of [concept].
Listen now: [link]
#NewMusic #HipHop
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Chars: 87/280 | Hashtags: 2 | Status: Within limits
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Actions:
[A] Approve — keep as-is
[R] Revise — give feedback for rewrite
[S] Shorten — make more concise
[P] Punch up — make more engaging/attention-grabbing
[H] Add hashtags — suggest relevant hashtags
[T] Rewrite tone — specify tone (casual, professional, hype, etc.)
[K] Skip — move to next without changes
After any revision action (R, S, P, H, T):
Revised version:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[revised copy here]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Chars: 142/280 | Hashtags: 3 | Status: Within limits
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[A] Approve this version
[R] Revise again — more feedback
[D] Discard — revert to original
Campaign files contain strategy tables and messaging, not code-block posts. Adjust the review approach:
After all sections for a platform are reviewed:
Updated twitter.md — 4 posts revised, 2 approved as-is, 1 skipped
Only write back if at least one section was revised. If all sections were approved as-is or skipped, skip the write step.
Between platforms, show a running summary:
## Review Progress
| Platform | Approved | Revised | Skipped | Limit Issues |
|----------|----------|---------|---------|--------------|
| Twitter | 4 | 2 | 1 | 0 |
| Facebook | — | — | — | — |
Next: Facebook (5 sections to review)
Continue? [Y/n]
After all platforms reviewed:
## Promo Review Complete
| Platform | Approved | Revised | Skipped |
|----------|----------|---------|---------|
| Campaign | 3 | 1 | 0 |
| Twitter | 4 | 2 | 1 |
| Facebook | 3 | 2 | 0 |
| **Total** | **10** | **5** | **1** |
Char limit compliance: All posts within platform limits
Files updated:
- promo/campaign.md (1 revision)
- promo/twitter.md (2 revisions)
- promo/facebook.md (2 revisions)
Next steps:
1. Review any skipped posts if needed
2. Add streaming links when available (replace [Streaming Link] placeholders)
3. Ready for release: /bitwize-music:release-director <album>
When revising posts, follow these principles:
[placeholder] text that needs real content