debug-migration

Diagnose PHP/Laravel to NestJS migration issues in data structures, translations, and routing.

Updated Mar 6, 2026

Search Tags:#debugging #api #php #migration #diagnostics #nestjs

Ready to run

npx skills add https://github.com/Dinhpham04/DA-KLTN_HOTEL_MANAGEMENT --skill debug-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-migration
Source: https://github.com/Dinhpham04/DA-KLTN_HOTEL_MANAGEMENT/tree/main/.agents/skills/debug-migration
Command: npx skills add https://github.com/Dinhpham04/DA-KLTN_HOTEL_MANAGEMENT --skill debug-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers diagnose and fix migration issues that arise during transitioning from PHP/Laravel to NestJS and from Japanese FE to Vietnamese FE, ensuring smooth data and API consistency.

Core Features & Use Cases

Migration Issue Diagnosis: Detects mismatches in API data shape, data types, translations, and routing.
Root Cause Analysis: Provides actionable insights for common problems like API response discrepancies, relation omissions, or data inconsistencies.
Use Case: When a frontend shows incorrect data or routes result in 404 errors after migration, this Skill guides the developer in pinpointing causes and implementing fixes.

Quick Start

Use the debug-migration skill to analyze the API response when a migration-related feature fails to load correctly and get immediate insights for resolution.

Frequently Asked Questions about debug-migration

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

FAQPage Schema

How do I diagnose API response discrepancies after migrating from Laravel to NestJS?▼

To diagnose API response discrepancies after migrating from Laravel to NestJS, analyze data structure mismatches and translation residuals. This process detects data shape inconsistencies and omissions, pinpointing causes for incorrect frontend data displays.

Why does my frontend show incorrect data or 404 routing errors following a NestJS migration?▼

Frontend incorrect data or 404 routing errors following a NestJS migration occur due to API data shape mismatches and translation residuals. Diagnostic analysis identifies these routing errors and data structure inconsistencies to restore consistent API behavior.

How do I resolve data structure mismatches and ensure data integrity during a PHP to NestJS transition?▼

To resolve data structure mismatches during a PHP to NestJS transition, perform root cause analysis on translation residuals and API data types. This ensures data integrity and consistent API behavior throughout the tech stack migration.

Can I detect translation residuals affecting API consistency when migrating from Japanese to Vietnamese frontends?▼

Yes, you can detect translation residuals affecting API consistency when migrating from Japanese to Vietnamese frontends. The diagnostic analysis identifies these translation mismatches to ensure smooth data and API consistency across stack transitions.

What is the best way to fix relation omissions and data type mismatches in a NestJS migration?▼

The best way to fix relation omissions and data type mismatches in a NestJS migration is to perform diagnostic root cause analysis. This provides actionable insights to resolve API response discrepancies and data inconsistencies effectively.