php-migration

Diagnose baserCMS PHP upgrade warnings and deprecations across PHP 8.2, 8.4, and 8.5.

194|141|Updated Feb 12, 2012
One-click install
npx skills add https://github.com/baserproject/basercms --skill php-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-migration
Source: https://github.com/baserproject/basercms/tree/main/.agents/skills/php-migration
Command: npx skills add https://github.com/baserproject/basercms --skill php-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose and fix baserCMS PHP upgrade issues caused by deprecations, signature changes, and behavior changes in newer PHP releases.

Core Features & Use Cases

  • Version-specific guidance: Organizes known PHP 8.2, 8.4, and 8.5 migration patterns so you can quickly match a warning to the right fix.
  • Safe refactoring recipes: Covers common problems such as dynamic properties, implicit nullable parameters, deprecated reflection calls, null offsets, and obsolete cleanup functions.
  • Practical baserCMS context: Points to real baserCMS migration scenarios, including plugin code, tests, and framework-adjacent compatibility issues.
  • Use case: When a test log shows a new deprecation after upgrading PHP, use this Skill to identify the cause, choose the correct remediation pattern, and keep the codebase compatible.

Quick Start

Ask the Skill to classify the PHP warning or fatal error from your baserCMS code and recommend the safest migration fix for the current PHP version.

Frequently Asked Questions about php-migration

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

FAQPage Schema
How do I fix PHP 8.2 dynamic property deprecation warnings in baserCMS plugins?

To fix PHP 8.2 dynamic property deprecation warnings in baserCMS, you must diagnose the deprecated property usage and apply version-aware remediation by either defining the property explicitly or using the AllowDynamicProperties attribute.

What causes implicit nullable parameter deprecation warnings when upgrading baserCMS to PHP 8.4?

Implicit nullable parameter deprecation warnings during a baserCMS PHP 8.4 upgrade are caused by parameters lacking explicit null types, requiring you to refactor function signatures to use explicit nullable declarations for compatibility.

How do I resolve nullable signature mismatches in PHP migration for baserCMS tests?

Resolving nullable signature mismatches in PHP migration for baserCMS tests involves diagnosing the incompatible method signatures and applying safe refactoring recipes to align parameter types with newer PHP runtime requirements.

Why does baserCMS throw fatal errors with null offsets after a PHP upgrade?

baserCMS throws fatal errors with null offsets after a PHP upgrade because newer PHP runtime versions enforce stricter null safety behavior changes, requiring you to diagnose the null offset access and apply version-specific code remediation.

Can this Skill diagnose deprecated reflection calls in baserCMS application code for PHP 8.5?

Yes, this Skill can diagnose deprecated reflection calls in baserCMS application code for PHP 8.5 by identifying the obsolete reflection methods and recommending the correct version-aware migration pattern to fix the compatibility issue.

What is the best way to handle obsolete cleanup function deprecations when upgrading baserCMS PHP versions?

The best way to handle obsolete cleanup function deprecations when upgrading baserCMS PHP versions is to classify the specific warning from your test logs and apply the recommended safe refactoring recipe to replace the deprecated function calls.