superpowers-sage:reviewing

Name: superpowers-sage:reviewing
Availability: InStock
Author: Hekivo

Audits Sage/Acorn PHP, Blade, ACF, and Tailwind code in pull-request workflows.

13|Updated Mar 19, 2026

Search Tags:#code review #tailwind #visual verification #wordPress #acorn #roots sage #php blade

Ready to run

npx skills add https://github.com/hekivo/superpowers-sage --skill superpowers-sage-reviewing-hekivo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-sage:reviewing
Source: https://github.com/hekivo/superpowers-sage/tree/main/skills/reviewing
Command: npx skills add https://github.com/hekivo/superpowers-sage --skill superpowers-sage-reviewing-hekivo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces PR review time and prevents convention drift in Sage/Acorn (Roots ecosystem) projects by systematically checking backend, Blade/ACF block patterns, frontend constraints, and architecture rules.

Core Features & Use Cases

Convention audit for Sage/Acorn code: Validates Service Provider structure, ACF block/field usage, Blade template responsibilities, and route/controller patterns.
Block-view guardrails for critical violations: Flags Tailwind/R-css-vars and component reuse issues, including hardcoded/invalid arbitrary value patterns and layout drift.
Design alignment checks (when plans provide specs): Reads plan asset specs and verifies implemented components against reference selectors/URLs.
Visual verification workflow: Dispatches visual verification for spec files to report MATCH/DRIFT/MISSING/FAIL_ARBITRARY_VALUES before merge.

Quick Start

Run a review for all changed files in your Sage/Acorn project by invoking the reviewing skill with no arguments.

Frequently Asked Questions about superpowers-sage:reviewing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit Sage and Acorn WordPress projects for convention drift in pull requests?▼

To audit Sage and Acorn projects for convention drift, review PHP service providers, ACF blocks, Blade templates, routes, and Tailwind usage. This process flags structural violations and layout drift across changed files before merging.

What is the best way to review Blade templates and ACF block patterns in Roots Sage?▼

Reviewing Blade templates and ACF block patterns in Roots Sage involves checking template responsibilities and validating field usage against established conventions. This identifies critical violations and maps line-specific issues for immediate correction.

Can I verify implemented Tailwind components against design specs during a code review?▼

Yes, you can verify implemented Tailwind components against design specs by reading plan asset specs and dispatching visual verification. This reports MATCH, DRIFT, MISSING, or FAIL_ARBITRARY_VALUES statuses for frontend alignment before merge.

Does the code review process flag hardcoded arbitrary values in Tailwind CSS?▼

Yes, the code review process flags hardcoded and invalid arbitrary value patterns in Tailwind CSS. It enforces block-view guardrails to prevent component reuse issues and layout drift in Sage/Acorn frontend implementations.

How do I check Service Provider structure and route patterns in an Acorn codebase?▼

Checking Service Provider structure and route patterns in an Acorn codebase requires auditing PHP controllers against architectural rules. This validation ensures backend conventions are maintained and surfaces categorized findings for improvements.