- Home
- Skills
- Frontend & Web Apps
- JavaScript to TypeScript Migration Planner and Tracker
Works with the AI Agents you already use
JavaScript to TypeScript Migration Planner and Tracker
Migrate a JS codebase to TypeScript in small batches with a strictness ladder, counted escape hatches and a CI typecheck. Verdict ON TRACK, STALLED or RISKY.
$5
JavaScript to TypeScript Migration Planner and Tracker
Example session with this skill installed
Our Express API is about 140 .js files, CommonJS, Jest, Node 24. Set up TypeScript so we can migrate gradually, convert the first batch of utility files, and tell me where we stand.
- Read your context and instructions
- Compiled the javascript to typescript
TS migration report: orders-api (2026-10-18)
Defaults used: batch of 5-15 files, zero new any, target strict: true
Stack: Express · CommonJS · tsc to dist/ · Jest · TypeScript 6.0.x (from npx tsc --version)
Phase: 0 (allowJs, checkJs off)
| Metric | Previous | Now |
|---|---|---|
| .js files | 140 | 131 |
| .ts files | 0 | 9 |
| tsc errors | n/a | 0 |
| any | 0 | 0 |
| @ts-expect-error | 0 | 1 |
| @ts-ignore / nocheck | 0 | 0 |
Config changes
{
"compilerOptions": {
"module": "nodenext",
"moduleResolution": "nodenext",
"allowJs": true,
"checkJs": false,
"strict": false,
"types": ["node", "jest"],
"outDir": "dist",
"skipLibCheck": true
},
"include": ["src"]
}
TypeScript 6.0 defaults strict to true and types to [], so both are set explicitly. Added "typecheck": "tsc --noEmit" and installed @types/express, @types/node, @types/jest.
Batch 1 (leaf utilities, 9 files)
src/utils/{date,money,slug,paginate,retry,env,logger,errors,ids}.js renamed with git mv in one commit, typed in a second. env.ts now parses process.env with zod instead of casting.
Escape hatches (every one)
- src/utils/logger.ts:14 · @ts-expect-error · legacy-log-sink ships no types for
flush()· add adeclare modulein batch 2
Next batch (in order)
src/models/*.js(6 files) - imported by 38 modules, only depend on utilssrc/clients/payments.js- response shape to validate with zod
Verdict: ON TRACK - tsc clean at Phase 0, tests pass, 9 files converted, no any added, one listed suppression.
Connects securely to your tools. The creator never sees your data.
About this skill
Most JavaScript to TypeScript migrations fail the same way: a big-bang rename, a wall of errors, and then any sprinkled everywhere until the compiler goes quiet. The project is technically TypeScript but no safer than before.
This skill runs the migration as a sequence of small, checkable steps and reports progress with real counts every time.
- Assesses the repo first: framework, ESM or CommonJS, build tool, test runner, JSDoc coverage, TypeScript and Node versions read from the project
- Writes a Phase 0 tsconfig with allowJs on and checkJs off, accounting for TypeScript 6.0+ defaults (strict on, types empty) that break naive setups
- Picks a build path per stack: Vite, Next.js built-in, tsc, tsx, or Node's native type stripping, with its syntax limits
- Orders files leaf-first from an import graph and renames them with git mv in separate commits so history survives
- Applies typing patterns: unknown over any, zod or type guards for API data, satisfies for config, as-const objects instead of enums
- Climbs a strictness ladder one flag at a time: noImplicitAny, strictNullChecks, strict
- Counts every any, ts-expect-error and ts-ignore with file and line, plus tsc errors and files remaining
- Adds a CI typecheck job with an escape-hatch budget
- Ends with a verdict: ON TRACK, STALLED or RISKY
For developers and tech leads moving Node, Express, React, Vue or Next.js apps to TypeScript who want a plan they can run batch by batch and a progress report they can paste into a PR.
Honesty note: the skill reports only numbers from commands it actually ran, marks unverified versions as such, and never hides errors by loosening tsconfig without showing the before and after counts. Version notes in the reference file reflect October 2026 docs and should be re-checked.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
Works incrementally and expects you to review each batch; it does not guarantee runtime equivalence beyond your existing tests. The any counter is pattern-based and misses implicit any from libraries. Version and flag notes reflect October 2026 documentation and may change. Monorepos with project references need manual tuning of the per-package configs.
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 buying a skill.
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 29 days ago
- Software
- Node.js and TypeScript (tsc)
Gittsc
Node.js
- Optional
- madge