typo3-rector

Apply Rector-based refactorings to migrate TYPO3 extensions from v13 to v14.

33|6|Updated Jan 2, 2026

Search Tags:#refactoring #migration #upgrade #typo3 #rector #dual-version

Ready to run

npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-rector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: typo3-rector
Source: https://github.com/dirnbauer/webconsulting-skills/tree/main/skills/typo3-rector
Command: npx skills add https://github.com/dirnbauer/webconsulting-skills --skill typo3-rector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TYPO3 upgrade migrations between major versions can be time-consuming and error-prone. Rector patterns provide automated refactoring to streamline upgrading v13 to v14 while maintaining compatibility and reducing manual rewrite work.

Core Features & Use Cases

Automated refactorings: Apply TYPO3 Rector rules to migrate extensions and custom code with minimal manual edits.
Dual-version compatibility: Patterns and configurations that support both TYPO3 v13 and v14, minimizing version drift.
Guided migration workflow: Step-by-step setup and running Rector to preview and apply changes across packages.

Quick Start

Install TYPO3 Rector as a dev dependency.
Create a rector configuration (rector.php) targeting your TYPO3 project.
Run Rector on the desired paths to apply upgrade rules.

Frequently Asked Questions about typo3-rector

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

FAQPage Schema

How do I automate TYPO3 extension upgrades from v13 to v14?▼

TYPO3 Rector automates extension upgrades from v13 to v14 by applying predefined refactoring rules to your codebase. You install it as a dev dependency, configure rector.php, and run it against your extension paths to apply the necessary migration changes.

Can I maintain dual-version compatibility for TYPO3 v13 and v14 extensions?▼

Yes, dual-version compatibility is supported through specific Rector patterns and configurations that allow your TYPO3 extensions to work with both v13 and v14, minimizing version drift during the migration period.

What is the best way to configure rector.php for a TYPO3 migration?▼

The best way to configure rector.php for a TYPO3 migration is to target your specific project paths and apply TYPO3 Rector rules, which guides the step-by-step setup and execution of automated upgrade refactorings across packages.

Does Rector support automated refactorings for custom TYPO3 code?▼

Yes, Rector supports automated refactorings for custom TYPO3 code by applying TYPO3 Rector rules to migrate extensions and custom codebases with minimal manual edits required during the upgrade process.

Why does upgrading TYPO3 extensions between major versions require automated refactoring?▼

Upgrading TYPO3 extensions between major versions requires automated refactoring because manual rewrites are time-consuming and error-prone, whereas Rector patterns streamline the process and reduce manual rewrite work significantly.