coding-php-legacy-maintainer

Inspect legacy PHP runtime shape, Composer dependencies, and version compatibility.

10|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcocello/dot-codex --skill coding-php-legacy-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-php-legacy-maintainer
Source: https://github.com/marcocello/dot-codex/tree/main/skills/coding-php-legacy-maintainer
Command: npx skills add https://github.com/marcocello/dot-codex --skill coding-php-legacy-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose, stabilize, and incrementally improve older PHP codebases without forcing a risky rewrite. It is designed for situations where runtime behavior, dependency constraints, and version compatibility matter more than architectural modernization.

Core Features & Use Cases

  • Runtime inspection: Review composer files, bootstrap paths, config, and entry points to understand the real application shape.
  • Safe maintenance and debugging: Identify dependency conflicts, deprecated APIs, missing extensions, and weak error handling while keeping changes small.
  • Upgrade planning: Map PHP version constraints, detect blockers, and choose the smallest viable upgrade path for legacy systems.
  • Use case: A framework-light PHP app fails after an environment change, and you need to confirm the current runtime setup, isolate the defect, and apply a minimal fix.

Quick Start

Use the coding-php-legacy-maintainer skill to inspect this PHP project, identify the runtime and dependency issues, and recommend the smallest safe fix.

Frequently Asked Questions about coding-php-legacy-maintainer

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

FAQPage Schema
How do I safely maintain and debug legacy PHP code without a full rewrite?

You can maintain legacy PHP code by inspecting runtime shapes, Composer dependencies, and entry points to apply minimal-risk fixes. This approach isolates defects and stabilizes older applications incrementally without forcing risky architectural rewrites.

What is the best way to plan a PHP version upgrade for a framework-light application?

Planning a PHP version upgrade requires mapping version constraints, detecting deprecated APIs and missing extensions, and choosing the smallest viable upgrade path. This verifies target compatibility before applying changes to framework-light legacy systems.

Why does my legacy PHP application fail after an environment change?

Legacy PHP applications fail after environment changes due to dependency conflicts, missing extensions, or deprecated APIs. Diagnosing the issue requires reviewing bootstrap paths and Composer files to confirm the current runtime setup and isolate the defect.

How do I identify dependency conflicts in a legacy PHP project?

Identifying dependency conflicts in a legacy PHP project requires inspecting Composer files and verifying version compatibility. This process detects deprecated APIs and missing extensions while keeping changes small to stabilize the application safely.

Can I upgrade PHP dependencies in a plain PHP codebase without breaking runtime behavior?

You can upgrade PHP dependencies in a plain PHP codebase by applying incremental validation and minimal-risk changes. Inspecting runtime shape and version constraints ensures that maintenance debugging preserves existing behavior while resolving conflicts.