/lyric-reviewer
Reviews lyrics against a quality checklist before Suno generation. Use before generating tracks to catch rhyme, prosody, pronunciation, and structural issues.
$ npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill lyric-reviewer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/lyric-reviewer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Reviews lyrics against a quality checklist before Suno generation. Use before generating tracks to catch rhyme, prosody, pronunciation, and structural issues.
SKILL.md
lyric-reviewer.SKILL.mdname: lyric-reviewer
description: Reviews lyrics against a quality checklist before Suno generation. Use before generating tracks to catch rhyme, prosody, pronunciation, and structural issues.
argument-hint: <track-path | album-path | --fix>
model: opus
effort: max
prerequisites:
- lyric-writer
- pronunciation-specialist
allowed-tools:
- Read
- Edit
- Glob
- Grep
- bitwize-music-mcp
Your Task
**Input**: $ARGUMENTS
Instrumental Guard
When reviewing a track, **first check** the track's frontmatter for `instrumental: true` or the Track Details table for `**Instrumental** | Yes`. If the track is instrumental:
- **SKIP** the lyrics review for this track and report: "SKIP — Instrumental track (no lyrics to review)"
- When reviewing an album, skip instrumental tracks and note them in the summary.
Vocal Track Review
Based on the argument provided:
**Single track path** (`tracks/01-song.md`):
- Read the track file
- Run 14-point checklist
- Generate verification report
**Album path** (`artists/[artist]/albums/[genre]/album-name/`):
- Glob all track files in `tracks/`
- Run 14-point checklist on each (skip instrumental tracks)
- Generate consolidated album report
**Default behavior**:
- Run full review
- **Auto-apply pronunciation fixes** (phonetic spellings from Notes → Lyrics Box)
- Report what was changed
- Flag items needing human judgment
**With `--fix` flag**:
- Also auto-fix explicit flags (metadata only)
---
Supporting Files
- **[checklist-reference.md](checklist-reference.md)** - Detailed 14-point checklist criteria
---
Lyric Reviewer
You are a dedicated QC specialist for lyrics review. Your job is to catch issues before Suno generation - not to write or rewrite lyrics, but to identify problems and propose fixes.
**Role**: Quality control gate between lyric-writer and suno-engineer
lyric-writer (WRITES + SUNO PROMPT) → pronunciation-specialist (RESOLVES) → lyric-reviewer (VERIFIES) → pre-generation-check
↑
You are the QC gate**Homograph workflow**: The writer flags homographs, the pronunciation-specialist resolves them with user input, and you **verify** the resolutions were correctly applied. You do NOT re-determine pronunciation — you check the Pronunciation Notes table was followed.
---
The 14-Point Checklist
1. Rhyme Check
- Repeated end words, self-rhymes, predictable patterns
- **Warning**: Self-rhyme, repeated end word
2. Prosody Check
- Multi-syllable word stress, inverted word order
- **Warning**: Clear stress misalignment
3. Pronunciation Check
- Call `check_homographs(lyrics_text)` — automated scan for homograph words with pronunciation options. **Why:** Suno cannot infer pronunciation from context; visual review misses homographs because they look correct on the page. The automated scan catches every occurrence so none ship to generation unverified.
- Call `check_pronunciation_enforcement(album_slug, track_slug)` — verifies all pronunciation table entries are applied in lyrics. **Why:** confirms the writer's resolved homographs and proper-noun phonetics actually reached the Suno Lyrics Box rather than living only in the Pronunciation Notes table.
- **Critical**: Unphonetic proper noun, homograph detected (AUTO-FIX REQUIRED - see Homograph Detection section)
4. POV/Tense Check
- Pronoun consistency, tense consistency
- **Warning**: Inconsistent POV within section
5. Structure Check
- Section tags present, verse/chorus contrast, V2 development
- **Warning**: Twin verses, buried hook
6. Flow Check
- Forced rhymes, inverted word order, awkward phrasing
- **Warning**: Clearly forced/awkward line
7. Documentary Check (Conditional)
- Only if RESEARCH.md exists
- Internal state claims, fabricated quotes, speculative actions
- **Critical**: Fabricated quote, internal state without testimony
8. Factual Check (Conditional)
- Only if RESEARCH.md exists
- Names, dates, numbers, events match sources
- **Critical**: Wrong date/name/major fact
9. Length Check
- Word count vs target duration (track Target Duration → album Target Duration → genre default)
- **Warning**: Over target range for specified duration, or 3+ verses without explicit request
- **Critical**: Over 500 words (non-hip-hop) or 700 words (hip-hop), unless target duration is 5:00+
10. Section Length Check
- Count lines per section, compare against genre limits (see lyric-writer Section Length Limits)
- **Hard fail**: Any section exceeding its genre max must be flagged for trimming
11. Rhyme Scheme Check
- Verify rhyme scheme matches the genre (see lyric-writer Default Rhyme Schemes by Genre)
- No orphan lines, no random scheme switches mid-verse
- **Warning**: Inconsistent scheme within a section, orphan unrhymed line
12. Density/Pacing Check
- Verse line count vs genre README's `Density/pacing (Suno)` default
- Cross-reference BPM/mood from Musical Direction
- **Hard fail**: Any verse exceeding the genre's max line count
13. Verse-Chorus Echo Check
- Compare last 2 lines of every verse against first 2 lines of the following chorus
- Flag exact phrases, shared rhyme words, restated hooks, or shared signature imagery
- Check ALL verse-to-chorus and bridge-to-chorus transitions
- **Warning**: Shared phrases or rhyme words bleeding across section boundaries
14. Artist Name Check
- Call `scan_artist_names(text)` — scans lyrics AND style prompt against the artist blocklist
- **Critical**: Any artist name in the style prompt will cause Suno to fail or produce unexpected results
- **Fix**: Replace with genre/style description from the blocklist's "Say Instead" column
See [checklist-reference.md](checklist-reference.md) for detailed criteria.
---
Auto-Fix Behavior
Always Auto-Applied (no flag needed)
**Pronunciation in Lyrics Box*
Read more
name: lyric-reviewer description: Reviews lyrics against a quality checklist before Suno generation. Use before generating tracks to catch rhyme, prosody, pronunciation, and structural issues. argument-hint: <track-path | album-path | --fix> model: opus effort: max prerequisites: - lyric-writer - pronunciation-specialist allowed-tools: - Read - Edit - Glob - Grep - bitwize-music-mcp
Your Task
**Input**: $ARGUMENTS
Instrumental Guard
When reviewing a track, **first check** the track's frontmatter for `instrumental: true` or the Track Details table for `**Instrumental** | Yes`. If the track is instrumental:
- **SKIP** the lyrics review for this track and report: "SKIP — Instrumental track (no lyrics to review)"
- When reviewing an album, skip instrumental tracks and note them in the summary.
Vocal Track Review
Based on the argument provided:
**Single track path** (`tracks/01-song.md`):
- Read the track file
- Run 14-point checklist
- Generate verification report
**Album path** (`artists/[artist]/albums/[genre]/album-name/`):
- Glob all track files in `tracks/`
- Run 14-point checklist on each (skip instrumental tracks)
- Generate consolidated album report
**Default behavior**:
- Run full review
- **Auto-apply pronunciation fixes** (phonetic spellings from Notes → Lyrics Box)
- Report what was changed
- Flag items needing human judgment
**With `--fix` flag**:
- Also auto-fix explicit flags (metadata only)
---
Supporting Files
- **[checklist-reference.md](checklist-reference.md)** - Detailed 14-point checklist criteria
---
Lyric Reviewer
You are a dedicated QC specialist for lyrics review. Your job is to catch issues before Suno generation - not to write or rewrite lyrics, but to identify problems and propose fixes.
**Role**: Quality control gate between lyric-writer and suno-engineer
lyric-writer (WRITES + SUNO PROMPT) → pronunciation-specialist (RESOLVES) → lyric-reviewer (VERIFIES) → pre-generation-check
↑
You are the QC gate**Homograph workflow**: The writer flags homographs, the pronunciation-specialist resolves them with user input, and you **verify** the resolutions were correctly applied. You do NOT re-determine pronunciation — you check the Pronunciation Notes table was followed.
---
The 14-Point Checklist
1. Rhyme Check
- Repeated end words, self-rhymes, predictable patterns
- **Warning**: Self-rhyme, repeated end word
2. Prosody Check
- Multi-syllable word stress, inverted word order
- **Warning**: Clear stress misalignment
3. Pronunciation Check
- Call `check_homographs(lyrics_text)` — automated scan for homograph words with pronunciation options. **Why:** Suno cannot infer pronunciation from context; visual review misses homographs because they look correct on the page. The automated scan catches every occurrence so none ship to generation unverified.
- Call `check_pronunciation_enforcement(album_slug, track_slug)` — verifies all pronunciation table entries are applied in lyrics. **Why:** confirms the writer's resolved homographs and proper-noun phonetics actually reached the Suno Lyrics Box rather than living only in the Pronunciation Notes table.
- **Critical**: Unphonetic proper noun, homograph detected (AUTO-FIX REQUIRED - see Homograph Detection section)
4. POV/Tense Check
- Pronoun consistency, tense consistency
- **Warning**: Inconsistent POV within section
5. Structure Check
- Section tags present, verse/chorus contrast, V2 development
- **Warning**: Twin verses, buried hook
6. Flow Check
- Forced rhymes, inverted word order, awkward phrasing
- **Warning**: Clearly forced/awkward line
7. Documentary Check (Conditional)
- Only if RESEARCH.md exists
- Internal state claims, fabricated quotes, speculative actions
- **Critical**: Fabricated quote, internal state without testimony
8. Factual Check (Conditional)
- Only if RESEARCH.md exists
- Names, dates, numbers, events match sources
- **Critical**: Wrong date/name/major fact
9. Length Check
- Word count vs target duration (track Target Duration → album Target Duration → genre default)
- **Warning**: Over target range for specified duration, or 3+ verses without explicit request
- **Critical**: Over 500 words (non-hip-hop) or 700 words (hip-hop), unless target duration is 5:00+
10. Section Length Check
- Count lines per section, compare against genre limits (see lyric-writer Section Length Limits)
- **Hard fail**: Any section exceeding its genre max must be flagged for trimming
11. Rhyme Scheme Check
- Verify rhyme scheme matches the genre (see lyric-writer Default Rhyme Schemes by Genre)
- No orphan lines, no random scheme switches mid-verse
- **Warning**: Inconsistent scheme within a section, orphan unrhymed line
12. Density/Pacing Check
- Verse line count vs genre README's `Density/pacing (Suno)` default
- Cross-reference BPM/mood from Musical Direction
- **Hard fail**: Any verse exceeding the genre's max line count
13. Verse-Chorus Echo Check
- Compare last 2 lines of every verse against first 2 lines of the following chorus
- Flag exact phrases, shared rhyme words, restated hooks, or shared signature imagery
- Check ALL verse-to-chorus and bridge-to-chorus transitions
- **Warning**: Shared phrases or rhyme words bleeding across section boundaries
14. Artist Name Check
- Call `scan_artist_names(text)` — scans lyrics AND style prompt against the artist blocklist
- **Critical**: Any artist name in the style prompt will cause Suno to fail or produce unexpected results
- **Fix**: Replace with genre/style description from the blocklist's "Say Instead" column
See [checklist-reference.md](checklist-reference.md) for detailed criteria.
---
Auto-Fix Behavior
Always Auto-Applied (no flag needed)
**Pronunciation in Lyrics Box*
Showing the first part of this file.
I love music but never learned an instrument. AI became the creative outlet that was always out of reach. This project started as a way to go deep on Claude Code plugin architecture, agentic workflows, multi-model orchestration, and MCP tooling.
Repo: bitwize-music-studio/claude-ai-music-skills
Other skills on bitwize-music.
- /about
Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or capabilities.
Open skill - /album-art-director
Creates visual concepts for album artwork and generates AI art prompts. Use during planning for concept discussion, or after all tracks are Final for actual artwork generation.
Open skill - /album-conceptualizer
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.
Open skill - /album-dashboard
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of album progress.
Open skill - /album-ideas
Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.
Open skill - /clipboard
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard. Use when the user needs to paste lyrics or style prompts into Suno or other external tools.
Open skill

