Skip to content
Back to skills

Revise Block Deep

ASecurity

Deep AI audit of all blocks or specific blocks — runs structural checks first, then uses AI to review content quality, descriptions, grammar, admin render justification, wrapper usage, and empty-state messages.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 13, 2026
ai-agentsphpbashnodefrontend

Security analysis

A100/100

Scanned October 13, 2026

npx -y skills add phucbm/skills --skill revise-block-deep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Revise Block Deep?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Revise Block Deep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/phucbm-revise-block-deep/badge)](https://www.skillsdirectory.com/skills/phucbm-revise-block-deep)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: revise-block-deep
description: Deep AI audit of all blocks or specific blocks — runs structural checks first, then uses AI to review content quality, descriptions, grammar, admin render justification, wrapper usage, and empty-state messages.
---

Read [`@/knowledge/acf-blocks/conventions.md`](../../knowledge/acf-blocks/conventions.md) and [`@/knowledge/acf-blocks/fields.md`](../../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

```bash
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.