l-text-review-article

Review the latest article using 3 parallel subagents and provide consolidated feedback on structure, style, and technical formatting.

Text Review Article Command

Review the latest article using 3 parallel code-reviewer subagents.

Your Task

1. Find the Target Article

Find the article in /src/mdx/notes/. Use these strategies in order:

1. Check current unstaged changes (PRIMARY) - Run git diff --name-only to see files with unstaged changes. This is the most likely target since the user just edited the file.
2. Check recent commits - Run git log --oneline -5 --name-only for recently committed files
3. Check file modification times - Use find src/mdx/notes -name "*.mdx" | xargs ls -lt | head -10

If unclear, use AskUserQuestion to let user choose from candidates.

2. Launch 3 Parallel Reviewers

Use the Task tool with subagent_type: "code-reviewer" to spawn 3 agents in parallel (single message with 3 Task calls).

Agent 1 prompt:

Review this MDX article with focus: Structure & Flow
File: [absolute path]

Read the writing rules first:
- doc/docs/writing/writing-style.md
- doc/docs/writing/markdown-writing-rule.md
- doc/docs/writing/vocabulary-rule.md

Check for:
- Logical flow between sections
- Clear introduction and conclusion
- Appropriate heading structure
- Smooth transitions between topics

Agent 2 prompt:

Review this MDX article with focus: Style & Voice
File: [absolute path]

Read the writing rules first:
- .claude/skills/_shared/writing-voice.md  (PRIMARY — project-wide rule:
  AI-written prose must be facts only; emotion/opinion is the human author's
  layer; flag any AI-style emotional flourishes that crept into the article)
- doc/docs/writing/writing-style.md
- doc/docs/writing/vocabulary-rule.md

Check for:
- AI-emotion violations: importance markers (ポイントは / 興味深いのは), dramatic
  emphasis (革命的), invented first-person reactions (自分も最初はそうでした),
  reader-anticipation flourishes (おおよそイメージがつくかも知れません) —
  treat any of these as critical issues to flag
- Consistent writing style (Takazudo's voice)
- Appropriate hedging expressions used as factual hedges, not as personality
  decoration
- Balance of formal/casual tone
- Reader-friendly prose

Agent 3 prompt:

Review this MDX article with focus: Technical & Formatting
File: [absolute path]

Read the writing rules first:
- doc/docs/writing/markdown-writing-rule.md

Check for:
- Proper MDX component usage
- Image references and alt text
- Code block formatting
- Link validity
- Frontmatter correctness

3. Consolidate and Present

After all 3 complete, consolidate feedback:

## Article Review: [filename]

### Critical Issues (Must Fix)

1. [Issue with location and suggested fix]

### Recommended Improvements

1. [Improvement with reasoning]

### Minor Suggestions

- [Small tweaks]

### What's Working Well

- [Positive feedback]

### Summary

[Top 3 action items]

Arguments

$ARGUMENTS - Optional: specific file path to review