check-migration-status

Audit MVC to Angular and ASP.NET Core migration progress by comparing controllers, views, endpoints, and routes.

6|1|Updated Dec 13, 2017
One-click install
npx skills add https://github.com/esassoc/neptune --skill check-migration-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-migration-status
Source: https://github.com/esassoc/neptune/tree/main/.claude/skills/check-migration-status
Command: npx skills add https://github.com/esassoc/neptune --skill check-migration-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of tracking and understanding the progress of migrating a legacy application (MVC) to a modern tech stack (Angular SPA + ASP.NET Core API). It provides a clear overview of which parts of the application have been successfully updated, are partially done, or have not yet been started.

Core Features & Use Cases

  • Comprehensive Auditing: Analyzes controllers, views, API endpoints, and frontend routes to determine migration status.
  • Status Categorization: Classifies entities into 'Migrated', 'Partial', 'Not Started', or 'New Only'.
  • Prioritization: Assesses migration priority based on business criticality, dependencies, and complexity.
  • Actionable Recommendations: Suggests quick wins, identifies critical dependencies, and highlights complex migrations.
  • Use Case: A development team lead can use this skill to quickly generate a report on the overall migration status of the Neptune application, identify immediate tasks, and plan future sprints effectively.

Quick Start

Run the check-migration-status skill to audit the migration progress from legacy MVC to Angular SPA.

Frequently Asked Questions about check-migration-status

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

FAQPage Schema
How do I audit migration progress from legacy MVC to Angular and ASP.NET Core?

To audit migration progress, compare legacy controllers and views against modern API endpoints and frontend routes. This process classifies entities as fully migrated, partially migrated, or not started, generating a detailed report with status and priority assessment.

What is the best way to track refactoring status from MVC to an Angular SPA?

Tracking refactoring status involves analyzing code components to categorize migration completeness. It identifies quick wins, critical dependencies, and complex migrations by comparing existing controllers and views with new API endpoints and Angular routes.

How does a code audit determine if an entity is partially migrated to ASP.NET Core?

A code audit determines partial migration by checking if an entity has either the backend API endpoint or the frontend route implemented, but not both. It compares the legacy MVC structure against the modern Angular and ASP.NET Core stack.

Can I prioritize migration tasks based on business criticality and dependencies?

Yes, you can prioritize migration tasks by assessing business criticality, dependencies, and complexity. The audit evaluates these factors to highlight quick wins and identify complex migrations that require immediate development attention.

Does the migration status report work without existing frontend routes?

The migration status report primarily relies on comparing frontend routes and API endpoints against legacy views and controllers. Without existing frontend routes, the audit cannot fully determine partial migration status for the Angular SPA architecture.