Scan code for legacy PatternFly CSS classes and recommend PF6-safe replacements. Use when upgrading from PF4/PF5 or auditing a codebase for deprecated class names.
Installs into .claude/skills of the current project.
Are you the author of Pf Css Migration Scan?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/rh-uxd-pf-css-migration-scan)
---
name: pf-css-migration-scan
description: Scan code for legacy PatternFly CSS classes and recommend PF6-safe replacements. Use when upgrading from PF4/PF5 or auditing a codebase for deprecated class names.
---
# PF Class Migration Scanner
Locate legacy PatternFly class names and migration risks.
When migration recommendations are ambiguous, query the PatternFly MCP server first to verify the latest supported component patterns and tokens.
## Migration scope
- Legacy versioned classes (`pf-v5-*`, `pf-v4-*`)
- Unversioned legacy classes (`pf-c-*`, `pf-u-*`, `pf-l-*`)
- Legacy token patterns (`--pf-v6-*`, `--pf-global-*`) that should use semantic tokens (`--pf-t--*`)
## Scan commands
```bash
rg "pf-v5-|pf-v4-|pf-c-|pf-u-|pf-l-" src
rg "--pf-v6-|--pf-global-" src
```
## Replacement guidance
- Prefer PatternFly React component props and composition first.
- If a utility class is still needed, use `pf-v6-u-*` variants.
- Prefer semantic tokens (`--pf-t--*`) over hardcoded values and legacy token names.
## Output format
For each finding include:
- file path
- current class/token
- recommended PF6 replacement
- confidence (`high`, `medium`, `low`)
Files in this skill
SKILL.md1.1 KB
eval/cases/legacy-token-patterns/_legacy-overrides.scss472 B
eval/cases/legacy-token-patterns/annotations.yaml107 B
eval/cases/legacy-token-patterns/input.yaml145 B
eval/cases/legacy-versioned-classes/LegacyNavbar.tsx926 B
eval/cases/legacy-versioned-classes/annotations.yaml144 B
eval/cases/legacy-versioned-classes/input.yaml129 B
