saas-migration-audit

Analyze JavaScript and TypeScript projects for SaaS stack migration feasibility.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill saas-migration-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: saas-migration-audit
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/saas-migration-audit
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill saas-migration-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, non-destructive analysis of existing JavaScript/TypeScript projects to determine feasibility, risks, and effort required to migrate to a canonical SaaS stack (Turborepo, Next.js, tRPC, Drizzle, Auth.js, Stripe, PageShell). The skill centralizes stack detection, gap classification, data migration risk assessment, and produces a clear migration plan so teams can decide whether to migrate, partially migrate, or rebuild.

Core Features & Use Cases

  • Automated Stack Detection: Scans manifests and common files to detect package manager, monorepo tooling, framework, ORM, auth, billing, CI/CD, and deployment patterns.
  • Gap Classification & Risk Scoring: Maps each layer to MATCH/COMPATIBLE/DIVERGENT/MISSING/CONFLICTING with quantitative risk assessment and impact/probability scoring.
  • Data & Auth Migration Assessment: Highlights schema, auth, and billing migration risks, and lists mitigation and rollback strategies for critical gaps.
  • Phased Migration Planning: Produces a dependency-aware, phase-by-phase migration plan with verification and rollback steps and estimated effort per phase.
  • Non-destructive Reporting: Generates a markdown audit report suitable for stakeholder review without making any changes to source code.

Quick Start

Ask the skill to analyze the repository at the given path and produce a phased markdown migration audit comparing the current stack to the canonical SaaS stack.

Frequently Asked Questions about saas-migration-audit

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

FAQPage Schema
How do I audit a Next.js monorepo for SaaS migration feasibility?▼

To audit a Next.js monorepo for SaaS migration, the skill scans manifests to detect framework, ORM, auth, billing, and CI/CD patterns, then produces a markdown report with gap classification and risk scoring.

What is a SaaS migration audit and how does risk scoring work?▼

A SaaS migration audit assesses existing JavaScript and TypeScript projects against a canonical stack, mapping layers like auth and ORM to MATCH or DIVERGENT statuses with quantitative impact and probability risk scoring.

Can I assess tRPC and Drizzle migration risks without modifying my source code?▼

Yes, you can assess tRPC and Drizzle migration risks without modifying source code because the skill performs non-destructive analysis, generating a stakeholder-ready markdown report while leaving files untouched.

How do I plan a phased migration to a canonical SaaS stack?▼

Plan a phased migration to a canonical SaaS stack by generating a dependency-aware plan from the audit, which includes verification steps, rollback strategies, and estimated effort per phase.

Does the migration audit support both single-repo and monorepo codebases?▼

Yes, the migration audit supports both single-repo and monorepo codebases, detecting package manager and monorepo tooling patterns to evaluate migration feasibility across different project structures.

When should I not use an automated SaaS stack migration audit?▼

You should not use an automated SaaS stack migration audit if your project lacks standard JavaScript or TypeScript manifests, as the tool relies on detecting specific framework, ORM, and CI/CD patterns from those files.