Reviews CSS/SCSS changes in the current branch for over-specificity, missed reuse opportunities, and over-engineered abstractions. Produces analysis findings and uses pm7y-ralph-planner to generate TASKS.md for autonomous execution. Use when reviewing CSS changes before commit or PR, or to audit existing styles. Supports @file syntax to target specific files.
View on GitHubpm7y/pm7y-marketplace
pm7y-claude-code
skills/pm7y-css-review/SKILL.md
January 22, 2026
Select agents to install to:
npx add-skill https://github.com/pm7y/pm7y-marketplace/blob/main/skills/pm7y-css-review/SKILL.md -a claude-code --skill pm7y-css-reviewInstallation paths:
.claude/skills/pm7y-css-review/# CSS/SCSS Review Skill Reviews CSS/SCSS changes for unnecessary complexity and missed reuse opportunities. Produces analysis findings that are passed to `pm7y-ralph-planner` for TASKS.md generation. --- ## Overview This skill analyzes CSS/SCSS files for three categories of issues: - **Over-specificity** - Complex selectors that could be simpler - **Missing reuse** - New styles that duplicate existing utilities - **Over-engineered abstractions** - Unnecessary mixins/variables/extends **Output:** Analysis findings passed to `pm7y-ralph-planner`, which generates a `TASKS.md` file with validation requirements and learnings tracking for autonomous execution via `pm7y-ralph-loop`. **When to use:** - Before committing CSS/SCSS changes - During PR review of style changes - Auditing existing stylesheets for cleanup - After rapid UI development to assess CSS debt --- ## Usage ``` /pm7y-css-review # Review all CSS/SCSS changes in branch /pm7y-css-review @path/to/file.scss # Review specific file only ``` --- ## Review Process ### Step 1: Determine Scope Parse arguments to determine which files to review: **If @file argument provided:** - Extract the file path after the @ symbol - Verify the file exists and is CSS/SCSS - Review only that file **If no arguments (default):** - Run `git diff main...HEAD --name-only` to find files changed in branch - Also check `git diff --name-only` for staged/unstaged changes - Filter to only `.css` and `.scss` files - If no CSS/SCSS files changed, report "No CSS/SCSS changes found" and stop ### Step 2: Build Style Inventory Scan the project to understand existing styles: **Find all style files:** ```bash # Find all CSS and SCSS files in project (exclude node_modules, dist, build) find . -type f \( -name "*.css" -o -name "*.scss" \) \ -not -path "*/node_modules/*" \ -not -path "*/dist/*" \ -not -path "*/build/*" \ -not -path "*/.next/*" ``` **Extract existing patterns:** For each style file, id