typescript-migration

Migrate JavaScript projects to TypeScript incrementally with phased configuration.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills --skill typescript-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-migration
Source: https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills/tree/main/skills/typescript-migration
Command: npx skills add https://github.com/Dedalus-ERP-PAS/hexagone-foundation-skills --skill typescript-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating large JavaScript codebases to TypeScript safely and progressively, without breaking existing functionality.

Core Features & Use Cases

  • Incremental strategy: migrate file by file starting from leaf nodes to minimize risk.
  • Config guidance: scaffold and tune tsconfig, type boundaries, and tooling for mixed JS/TS projects.
  • Real-world scenario: convert a legacy app step by step, gradually introducing strict types while preserving runtime behavior.

Quick Start

Rename a leaf JavaScript file to .ts and begin adding type annotations, progressively tightening the TypeScript configuration as you migrate.

Frequently Asked Questions about typescript-migration

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

FAQPage Schema
What is the best way to migrate a large JavaScript project to TypeScript?

The best way to migrate JavaScript to TypeScript is incrementally, starting by renaming leaf files to .ts and adding type annotations, then progressively tightening your tsconfig to minimize risk.

How do I configure tsconfig for a mixed JS and TS codebase?

Configure tsconfig for mixed JavaScript and TypeScript projects by enabling allowJs, tuning type boundaries, and progressively introducing strict checks as you migrate file by file from leaf nodes.

Can I add type safety to a legacy JavaScript app without breaking existing functionality?

You can add type safety to a legacy JavaScript app without breaking functionality by applying a phased migration approach, converting files step by step and gradually introducing strict types.

Why should I start a TypeScript migration with leaf files?

Start a TypeScript migration with leaf files to minimize dependency conflicts and risk, ensuring safe state transitions between migration phases as you progressively introduce types upward.

Does gradual TypeScript migration work for legacy codebases with no existing types?

Gradual TypeScript migration works for legacy codebases with no existing types by scaffolding tooling for mixed JS/TS projects and progressively adding type annotations and strict checks.