pf-class-migration-scanner

Scan codebases for legacy PatternFly classes and generate PF6-safe replacements.

10|26|Updated Jul 8, 2025
One-click install
npx skills add https://github.com/patternfly/ai-helpers --skill pf-class-migration-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pf-class-migration-scanner
Source: https://github.com/patternfly/ai-helpers/tree/main/plugins/design-foundations/skills/pf-class-migration-scanner
Command: npx skills add https://github.com/patternfly/ai-helpers --skill pf-class-migration-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans for legacy PatternFly class usage in codebases and recommends PF6-safe replacements to streamline modernization.

Core Features & Use Cases

  • Detects legacy PF class patterns (pf-v5-, pf-v4-, pf-c-, pf-u-, pf-l-, and legacy token patterns (--pf-v6-, --pf-global-*))
  • Suggests PF6-compatible alternatives and token usage
  • Use case: upgrading an older PatternFly project to PF6 to identify risky class names and generate migration notes.

Quick Start

Run the scanner on a codebase to generate a PF6 migration report with recommended replacements.

Frequently Asked Questions about pf-class-migration-scanner

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

FAQPage Schema
How do I find legacy PatternFly classes in my codebase before upgrading to PF6?

The scanner detects PF5, PF4, unversioned pf-c, pf-u, pf-l prefixes, and legacy token patterns like --pf-global-* across CSS, HTML, and JavaScript files to prepare your codebase for a PF6 migration.

What is the best way to generate a PatternFly 6 migration report?

Run a regex scanner over your project files to identify outdated PatternFly classes and output findings with file paths, current classes, recommended PF6 replacements, and confidence levels for an accurate migration report.

Does the PatternFly migration scanner work with CSS, HTML, and TypeScript files?

Yes, the PatternFly migration scanner analyzes CSS, HTML templates, and JavaScript/TypeScript sources to identify legacy PF class names and token patterns across your entire codebase comprehensively.

How do I replace legacy PatternFly tokens like --pf-global-* with PF6-safe alternatives?

Scan your codebase for outdated patterns like --pf-global-* and --pf-v6-* to receive recommended PF6-compatible token alternatives generated by the migration scanner with confidence ratings.

Can I verify PF6 component patterns during a code migration audit?

The migration scanner can query the PatternFly MCP server during a code audit to verify the latest component patterns and ensure recommended PF6 replacements are accurate and up-to-date.

What are the limitations of using regex scans for PatternFly class migration?

Regex scans identify legacy PatternFly class names and token patterns accurately but rely on confidence levels for replacements, which may require manual review for complex component logic.