Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    JavaScript to TypeScript Migration Planner and Tracker

    1

    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

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    JavaScript to TypeScript Migration Planner and Tracker

    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)

    MetricPreviousNow
    .js files140131
    .ts files09
    tsc errorsn/a0
    any00
    @ts-expect-error01
    @ts-ignore / nocheck00

    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 a declare module in batch 2

    Next batch (in order)

    1. src/models/*.js (6 files) - imported by 38 modules, only depend on utils
    2. src/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.

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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 29 days ago

    Requires

    Node.js and TypeScript (tsc)
    Git
    madge, optional (for the import graph)
    tsc
    Node.js
    madge

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    A SKILL.md with the step-by-step migration workflow, verdict rules and report template, and references/ts-migration-reference.md with tsconfig snippets for each phase, Node type stripping limits, TypeScript 6.0 and 7.0 version notes, typing patterns, a GitHub Actions typecheck job and the source URLs.

    Any agent that loads SKILL.md skills, such as Claude Code, Codex CLI, Cursor, VS Code Copilot and Gemini CLI. It needs terminal access to run tsc, grep and git.

    Unzip the folder into your agent's skills directory (for example .claude/skills/ in your project), then ask the agent to plan or continue a TypeScript migration. It asks a few questions once and proceeds with stated defaults.

    It does not convert a large codebase in one pass; it works batch by batch. The escape-hatch counter is grep-based, so it can miss any that comes from inference or library types. Version notes are as of October 2026 and need re-checking.

    A plain request tends to rename everything at once and add any to make errors go away. This skill fixes the order (leaf-first), keeps renames in separate commits, raises strictness one flag at a time, lists every suppression with file and line, and gives a verdict based on measured counts.

    New in Frontend & Web Apps