WordPress PHP Upgrade Preflight

    2

    Your host says PHP 7.4 / 8.0 / 8.1 is going away, or a PHP security release means you must move to a supported branch.

    Free

    5 uses4.0 (1 review)

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    WordPress PHP Upgrade Preflight

    Example session with this skill installed

    Our host says PHP 7.4 will be retired next month. Before we switch our WordPress shop to PHP 8.3, check what will break. Production is /var/www/shop, and there is a staging copy at /var/www/staging-shop.

    • Read your context and instructions
    • Compiled the wordpress php upgrade

    Summary

    Example site (sample output). Web PHP

    7.4.33, CLI PHP 8.1, target

    8.3. Verdict:

    ready after fixes - 2 blockers, 5 warnings, 11 deprecations. A full backup from today exists; PHP can be switched back from the host panel in about 5 minutes.

    Blockers (fix before switching)

    ComponentVersionProblemEvidenceFix
    shop-child (theme)customcreate_function() removed in PHP 8.0functions.php:212Replace with an anonymous function
    legacy-contact-form (plugin)2.1.0, no release since 2019each() removed in PHP 8.0; fatal on form submitincludes/mailer.php:88, debug.log on stagingReplace with a maintained form plugin

    Warnings and deprecations

    ComponentProblemEvidenceFix
    shop-childDynamic properties (8.2)debug.log, 6 entriesDeclare properties
    invoice-pdf (plugin)utf8_encode() deprecated (8.2)lib/pdf.php:41Update to 3.4 (available)
    shop-childstrftime() deprecated (8.1)inc/dates.php:17Use wp_date()

    Upgrade plan

    1. Take a fresh backup and confirm the restore steps.
    2. On staging: update invoice-pdf, replace legacy-contact-form, patch shop-child.
    3. Switch staging to PHP 8.3 and retest home, product, cart, checkout, contact and admin screens.
    4. Switch production in a quiet hour, purge the page cache, retest the same pages.
    5. Keep the rollback ready for 24 hours.

    Not checked

    Premium plugin payment-gateway-x is encoded, so it was not scanned. Ask the vendor to confirm PHP 8.3 support.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Your host says PHP 7.4 / 8.0 / 8.1 is going away, or a PHP security release means you must move to a supported branch. The hard part is not clicking the PHP switch. It is knowing what will break before you click it.

    This skill makes your agent do the preflight a WordPress maintenance engineer would do, and hand you a report you can act on.

    What it does

    1. Finds the PHP version the site really runs on (web vs CLI are often different) and any .htaccess / .user.ini pins that override the control panel.
    2. Inventories core, themes, plugins, must-use plugins and drop-ins with WP-CLI, including declared Requires PHP headers and pending updates.
    3. Scans code for incompatibilities: uses phpcs + PHPCompatibilityWP if you already have it, otherwise the bundled read-only grep triage script.
    4. Guides a runtime check on a staging copy: what to enable, which pages to hit, and how to classify debug.log entries into blockers, warnings and deprecations (null-to-string calls and dynamic properties only show up here).
    5. Checks backup and rollback: today's backup, how to switch PHP back, which caches to purge.
    6. Writes the report: verdict, blockers with file:line evidence, warnings, an ordered upgrade plan, and an explicit "not checked" list.

    Safety

    • Read-only. It never updates plugins, never edits php.ini, .htaccess or wp-config.php, never switches the PHP version.
    • Never prints wp-config.php contents. Database passwords, keys and salts stay out of the output.
    • No network calls. Nothing is installed without your approval.

    What's inside

    • SKILL.md - the step-by-step workflow and report template
    • references/php-version-changes.md - PHP 7.0 to 8.4 changes that break WordPress code, each with the usual fix
    • scripts/scan-php-compat.sh - read-only grep triage scan (bash + grep), tested against sample code for false positives

    Requirements

    Shell access to the site files (ideally a staging or local copy) and WP-CLI. PHP_CodeSniffer with PHPCompatibilityWP is optional but recommended.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.

    Read-only: does not edit files or change PHP versions. Requires WP-CLI. Patterns may miss logic errors that only occur at runtime. Staging environment needed for full log analysis.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    4.0
    1 review
    5
    0
    4
    1
    3
    0
    2
    0
    1
    0

    This skill has been used 5 times.

    Trust & safety

    Security scan

    Security scan passed 21 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Read Files

    File Scopes

    wp-content/**
    .htaccess
    .user.ini

    Shell is used only for read-only commands: php -v, WP-CLI list/get commands, grep and the bundled scan script. The skill does not write files, change settings or make network requests.

    Listed21 days ago

    What's inside

    Frequently Asked Questions

    The skill identifies deprecated functions, syntax changes, and library removals that cause fatal errors when moving to PHP 8.x, ensuring your site doesn't crash upon upgrading.

    This skill requires access to WP-CLI and the site's filesystem to perform its scan; it is designed to work with AI agents that have terminal or SSH execution capabilities.

    No, the skill operates in a non-destructive, read-only mode to inventory and analyze your site; it provides a roadmap of fixes but will not modify your code or change your server settings.

    Yes, the preflight check is designed to scan core files, active plugins, must-use (MU) plugins, and custom themes to ensure a comprehensive overview of the entire environment.

    You receive the full skill logic for auditing environments, the prioritized roadmap generation templates, and the integration scripts for standard static analysis tools.

    New in APIs & Backend

    Free