pf-analyze-modifiers

To audit PatternFly modifiers, analyze your SCSS codebase to discover pf-m-* classes, count usage frequencies, and validate design-system conformance. This generates Markdown reports with per-component statistics and global modifier mappings.

Yes, you can scope PatternFly CSS analysis to a single component or directory to generate targeted reports. By default the analysis applies to all components project-wide, but optional scoping narrows the modifier audit to specific source code locations.

The best way to document PatternFly pf-m-* classes for CSS consistency is to run a codebase analysis that produces Markdown reports. These reports summarize per-component mappings, global modifier statistics, and recommended cleanups to improve maintainability.

You validate PatternFly design-system conformance by analyzing your source code to identify pf-m-* modifiers and check consistency across SCSS files. This audits modifier coverage and highlights deviations from standard PatternFly classes.

No specific dependencies are required to analyze PatternFly modifiers in your project. The analysis operates directly on your project's SCSS files and source code to identify pf-m-* classes and generate usage reports without external tooling.