bali-view-audit

Audit Rails view templates for raw HTML and incorrect Bali ViewComponent usage.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill bali-view-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bali-view-audit
Source: https://github.com/Grupo-AFAL/claude-plugins/tree/main/rails-tools/skills/bali-view-audit
Command: npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill bali-view-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many Rails projects mix raw HTML and manual UI wiring with Bali ViewComponents, leading to inconsistent UI, duplicated patterns, and fragile Stimulus wiring; this Skill identifies those issues and recommends verified component replacements to improve maintainability and correctness.

Core Features & Use Cases

  • Anti-pattern detection: Finds incorrect Bali API usage such as deprecated parameters, wrong slot calls, and form builders missing Bali::FormBuilder.
  • Raw HTML replacement identification: Locates high-impact structural candidates (tables, page layouts, cards, modals) and repeated UI patterns that should use Bali components.
  • Verified suggestions & reporting: Produces prioritized findings with file locations, current code excerpts, and replacement suggestions that must be verified against the bali-components reference.
  • Use Case: Run a project-wide audit to convert manual tables and admin layouts into Bali::DataTable and Bali::AppLayout components and fix form builders across the codebase.

Quick Start

Run an audit of app/views/ to list HIGH priority Bali component replacements with code examples and verified API references.

Frequently Asked Questions about bali-view-audit

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

FAQPage Schema
How do I find raw HTML in Rails views that should use ViewComponents?

To find raw HTML in Rails views that should use ViewComponents, run an audit of app/views/ and app/components/ to locate structural candidates like tables, cards, and modals. The audit produces prioritized replacement opportunities with file locations and verified code snippets.

What are common Bali ViewComponent anti-patterns in Rails projects?

Common Bali ViewComponent anti-patterns include deprecated parameters, wrong slot calls, and forms missing the Bali::FormBuilder. An audit detects these incorrect usages and provides verified replacement suggestions referencing the component documentation.

Can I audit my Rails codebase for incorrect Bali component usage?

Yes, you can audit your Rails codebase for incorrect Bali component usage by scanning app/views/ and app/components/. The audit detects anti-patterns, identifies migration candidates, and outputs prioritized findings with verified component replacements.

How do I migrate manual Rails tables and layouts to Bali components?

To migrate manual Rails tables and layouts to Bali components, run a project-wide audit to identify high-impact structural candidates. The audit produces prioritized findings with current code excerpts and verified replacements like Bali::DataTable and Bali::AppLayout.

Why are my Rails form builders not working with Bali components?

Rails form builders fail with Bali components when missing the Bali::FormBuilder or using deprecated parameters. An audit detects incorrect form builder usage across the codebase and provides verified corrections referencing the Bali component API.