cells-cleanup

Automate code-quality cleanup for BBVA Cells/Lit components without changing logic or public APIs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cells-cleanup
Source: https://github.com/PixelDroid19/cells-agents/tree/main/skills/cells-cleanup
Command: npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sweep a Cells/Lit component for code quality issues without changing logic or behavior, reducing debt and improving maintainability.

Core Features & Use Cases

  • Enforces consistent formatting, JSDoc, attribute naming, and lifecycle hygiene without altering public APIs.
  • Applies common refactoring patterns (Rules of 2, mapping config, split renders) to improve readability and reliability.
  • Useful for teams enforcing coding standards across BBVA Cells components during reviews, migrations, and CI checks.

Quick Start

Run the cleanup pass on a target Cells/Lit component and review suggested non-breaking improvements before merging.

Frequently Asked Questions about cells-cleanup

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

FAQPage Schema
How do I clean up LitElement code without changing component behavior?

Code cleanup for LitElement components enforces formatting, JSDoc, and lifecycle hygiene without altering public APIs or logic. Apply refactoring patterns like Rules of 2 and split renders to improve readability and reliability while preserving behavior.

What is the best way to enforce coding standards across BBVA Cells components?

Enforcing coding standards across BBVA Cells components requires an automated cleanup pass checking formatting, attribute naming, and test cleanliness. Generate a structured report flagging risky changes for review during migrations or CI checks.

Can I automate JSDoc and attribute field generation for web-components?

Automating JSDoc and attribute field cleanup for web-components happens during the code-quality pass. The process enforces consistent documentation and attribute naming without changing public APIs or component logic.

Does code cleanup for Lit components require a specific repository structure?

Code cleanup for Lit components requires a valid SKILL.md frontmatter in the repository. Optional directories for scripts, references, and assets can be included to output a structured report flagging risky changes for review.

How do I fix LitElement lifecycle issues without breaking public APIs?

Fix LitElement lifecycle issues through an automated cleanup pass enforcing lifecycle hygiene and applying refactoring patterns like mapping config and split renders. This improves reliability without changing logic or public APIs.