Revise Block Deep

Read @/knowledge/acf-blocks/conventions.md and @/knowledge/acf-blocks/fields.md, then:

Usage

/wp-acf-blocks:revise-block-deep                 # all blocks
/wp-acf-blocks:revise-block-deep hero-banner     # single block
/wp-acf-blocks:revise-block-deep hero-banner faq # multiple blocks

Step 1 — Structural check

node $(claude plugin path wp-acf-blocks)/scripts/revise-block.js [block-slug...]

If there are ✗ issues, tell the user to fix them before proceeding. Warnings are fine to continue.

Step 2 — AI content review

For each block (or the specified blocks) read block.json, fields.json, render.php, render-admin.php (if exists) and check:

• Title and description — clear, human-readable, no placeholders, no grammar errors
• ACF field labels — meaningful, no defaults like "Text" or "Field Label", no typos. Never suggest changing name or key.
• Wrapper — render.php must use theme_get_block_wrapper_attributes() (theme helper in helpers/ui/), not the WP native get_block_wrapper_attributes(), never build wrapper attributes manually
• Admin render justification — render-admin.php only for interactive/hidden-content blocks; flag static blocks that have it unnecessarily, and interactive blocks that are missing it
• Empty states — render-admin.php must show a placeholder when content is empty; render.php must render nothing on the frontend when content is missing
• render.php cleanliness — no commented-out code, no leftover scaffold comments
• view.entry.ts — if block has frontend JS, source is view.entry.ts (compiled to view.js by tsup); flag if view.js exists with no view.entry.ts source (untracked compiled output)

Output format

{block-name}
  Structural:   ✔ passed
  Title:        ✔ clear
  Description:  ✗ "Sample description" — generic, update it
  Fields:       ⚠ field "text_1" has a generic label
  Wrapper:      ✔ uses theme_get_block_wrapper_attributes()
  Admin render: ✔ justified
  Empty states: ⚠ missing placeholder in render-admin.php
  View JS:      ✔ view.entry.ts present, view.js declared in viewScript

End with a summary count, then ask: "Fix all issues automatically? (or specify which blocks/rules to fix)" — only proceed after confirmation.