- Home
- Skills
- Frontend & Web Apps
- nextjs app router migration verifier
Works with the AI Agents you already use
nextjs app router migration verifier
Migrate Next.js routes to App Router with mandatory verification of cache semantics and component boundaries.
$18
nextjs app router migration verifier
Example session with this skill installed
Migrate pages/profile/[id].tsx which uses getServerSideProps to fetch user data and next/head for the title.
- Read your context and instructions
- Compiled the nextjs app router
I have analyzed the source. The original uses getServerSideProps (always fresh). Converted to App Router: fetch now includes { cache: 'no-store' } to prevent stale data. The next/head block is now a generateMetadata function. Awaiting your review of these specific diffs before proceeding.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Migrating from Next.js Pages Router to App Router is prone to silent regressions. Standard build checks and type systems cannot detect when a fresh getServerSideProps call is replaced by a default fetch, which Next.js caches by default, leading to stale data bugs in production.
What it does
- Performs a mandatory before/after comparison of data-fetching cache semantics, ensuring
getServerSidePropsandgetInitialPropsare correctly ported to{ cache: 'no-store' }. - Identifies and migrates
next/headtags to the Metadata API to prevent SEO tags from silently disappearing. - Verifies async conversion for
cookies()andheaders()to catch missing awaits that pass linting but fail at runtime. - Audits the Server/Client Component boundary to ensure internal database fields or API keys do not leak into the browser bundle.
- Converts legacy
getStaticPathsandfallbacklogic togenerateStaticParamsanddynamicParams.
Frameworks & tools
Next.js (Pages Router and App Router), React, TypeScript.
Why this beats prompting it yourself
General LLM prompts often hallucinate that fetch() is a drop-in replacement for legacy data methods, missing the critical caching default change. This skill enforces a hard stop between routes, preventing the "unsupervised bulk migration" pattern that causes developers to overlook layout-level fetching bugs and metadata omissions.
Use cases
- Converting complex authenticated routes that rely on per-request data freshness.
- Refactoring SEO-heavy marketing pages from legacy
next/headblocks to the modern Metadata API. - Moving Node.js-based API routes to Web-standard Route Handlers.
- Verifying that new
layout.jsdata fetching does not inadvertently cache user-specific data.
Known limitations
Does not handle middleware.ts logic or differences. Requires a manual review stop after every single route conversion to ensure accuracy.
Middleware behavior is out of scope. Migration is strictly one route at a time; bulk codebase conversion is explicitly disabled to prevent unverified regressions.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago