Copy Review

---
description: Review copy for clarity, tone, jargon, CTAs, SEO, and readability
allowed-tools: Read, Glob
---

# Copy Review

Read a file containing marketing copy, documentation, or product messaging and produce a structured review with specific, actionable rewrites.

The file to review: $ARGUMENTS

## Steps

1. **Read the target file** specified in $ARGUMENTS. If no file is specified, glob for `README.md`, `**/landing*`, `**/index.html`, or `**/about*` and review the most prominent one.

2. **Read surrounding context** to understand the product:
   - Read `README.md` if the target file is not the README itself.
   - Glob for `package.json` or equivalent to get product metadata.
   - Glob for other marketing or docs files to check tone consistency across the project.

3. **Analyze clarity** (score 1-10):
   - Identify sentences that are too long (>25 words) or convoluted.
   - Flag passive voice where active would be stronger.
   - Highlight ambiguous pronouns or unclear referents.
   - Check that the first paragraph answers: What is this? Who is it for? Why should I care?
   - For each issue, provide a specific rewrite.

4. **Analyze tone consistency** (score 1-10):
   - Characterize the overall tone (professional, casual, technical, friendly, authoritative).
   - Flag sentences that break from the dominant tone.
   - Check for consistency between headings and body text.
   - Note any unintentional tone shifts (e.g., casual intro then suddenly formal).

5. **Analyze jargon level** (score 1-10, where 1 = no jargon, 10 = extremely technical):
   - List every jargon term or acronym used.
   - For each, assess whether the target audience would understand it.
   - Suggest plain-language alternatives where appropriate.
   - Flag "curse of knowledge" moments where the writer assumes too much.

6. **Analyze calls to action** (score 1-10):
   - Identify all CTAs (explicit and implicit).
   - Assess each CTA for: specificity, urgency, value clarity, and placement.
   - Flag pages or sections with no CTA.
   - Suggest stronger CTA alternatives with specific copy.

7. **Analyze SEO opportunities**:
   - Identify the likely primary keyword/topic.
   - Check heading hierarchy (H1, H2, H3) for keyword inclusion.
   - Flag missing meta-description opportunities.
   - Suggest 3-5 related keywords that could be naturally incorporated.
   - Check for internal/external link opportunities.

8. **Assess readability**:
   - Estimate the Flesch-Kincaid grade level.
   - Flag paragraphs that are too dense (>4 sentences).
   - Check for adequate use of formatting (lists, bold, headings) to aid scanning.
   - Verify the content works when skimmed (headings tell the full story).

9. **Assess emotional resonance** (score 1-10):
   - Does the copy connect with a pain point or aspiration?
   - Are there concrete examples or stories that make it relatable?
   - Does it create a sense of "this is for me"?

10. **Produce the final review** in this structure:
    - Overall score (average of all dimensions)
    - One-paragraph executive summary
    - Detailed findings per dimension (score + specific issues + rewrites)
    - Top 5 highest-impact changes to make first
    - Rewritten version of the opening paragraph incorporating all feedback

## Rules

- Always provide specific rewrite suggestions, not just critiques.
- Frame feedback constructively — explain why a change improves the copy.
- Consider the likely audience based on the product type and context.
- Do not rewrite the entire file unless asked — focus on the most impactful changes.
- Respect the original voice and intent; improve, do not replace the author's style.