tsconfig-hardening

Inventory and harden TypeScript configurations in a monorepo with batched flag changes.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill tsconfig-hardening
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tsconfig-hardening
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/tsconfig-hardening
Command: npx skills add https://github.com/matt-riley/agent-skills --skill tsconfig-hardening

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tighten and rationalize TypeScript configuration safely, especially when enabling stricter compiler checks incrementally.

Core Features & Use Cases

  • Inventory and normalize tsconfig extends chains across packages.
  • Propose small, testable flag changes while preserving emit/build behavior.
  • Guardrails for incremental hardening with baseline checks and re-validations.

Quick Start

Begin by inventorying the tsconfig chain, then apply one targeted flag change and re-check typechecking.

Frequently Asked Questions about tsconfig-hardening

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

FAQPage Schema
How do I enable strict TypeScript compiler checks without breaking my monorepo build?

Incremental TypeScript hardening uses a batched workflow: capture a baseline configuration, apply one isolated strict flag change, and revalidate typecheck and build after each step to avoid breaking mixed module setups.

What is the best way to normalize tsconfig extends chains across multiple packages?

Normalizing tsconfig extends chains requires inventorying multi-package configurations first, then applying small testable flag changes while preserving emit behavior to maintain build stability across the repository.

Can I upgrade TypeScript strictness gradually across repositories with mixed module setups?

Yes, gradual strictness upgrades work by applying a safe batched workflow that captures a baseline, isolates individual flag changes, and revalidates builds, supporting mixed module setups across multi-package tsconfig chains.

Why does enabling strict mode in my TypeScript configuration break my typecheck?

Enabling strict mode breaks typecheck because multiple flags change simultaneously; incremental hardening solves this by applying isolated flag changes with baseline checks and revalidation after each step.

Do I need a baseline capture before tightening TS config in a monorepo?

Yes, baseline capture is required before tightening TS config to establish a safe reference point, enabling incremental hardening workflows to validate typecheck and build behavior after each isolated flag modification.