typecheck-preservationist

Resolve TypeScript type errors in the Aralia codebase with minimal fixes.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/Gambitnl/Aralia --skill typecheck-preservationist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typecheck-preservationist
Source: https://github.com/Gambitnl/Aralia/tree/main/skills/typecheck-preservationist
Command: npx skills add https://github.com/Gambitnl/Aralia --skill typecheck-preservationist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses and resolves TypeScript type errors within the codebase, ensuring code integrity and preventing regressions while adhering to strict preservationist principles.

Core Features & Use Cases

  • Automated Type Checking: Runs npm run typecheck to identify TypeScript errors.
  • Preservationist Fixes: Applies minimal, behavior-preserving changes to resolve errors, prioritizing adding types and type guards over refactoring or deletion.
  • Debt Flagging: Uses specific prefixes (// DEBT:, // HACK:, // TODO(next-agent):) to mark temporary solutions or areas requiring future attention.
  • Use Case: When a new feature introduces type errors, this Skill can be used to clean them up systematically, ensuring the codebase remains type-safe without altering existing functionality.

Quick Start

Run the typecheck preservationist skill to fix the first 10 typecheck errors.

Frequently Asked Questions about typecheck-preservationist

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

FAQPage Schema
How do I fix TypeScript type errors without changing existing code behavior?

To fix TypeScript type errors while preserving behavior, run an automated typecheck and apply minimal changes like explicit types and type guards. This ensures structural integrity by avoiding broad refactors or feature deletion during error resolution.

What is the best way to resolve TypeScript typecheck errors incrementally?

Resolving TypeScript typecheck errors incrementally involves running the type checker and fixing a small batch of errors at a time. This phased approach reduces the error count to zero while maintaining codebase stability and preventing regressions.

Can I flag temporary type assertions for future TypeScript debugging?

Yes, you can flag temporary type assertions during TypeScript debugging by using specific debt prefixes like `// DEBT:`, `// HACK:`, or `// TODO(next-agent):`. This marks areas requiring future attention without halting the current typecheck resolution.

Does typecheck preservation work with standard npm type checking scripts?

Yes, typecheck preservation works with standard npm type checking scripts by executing `npm run typecheck` to identify errors. It then applies behavior-preserving fixes to the codebase, ensuring type safety without altering existing functionality.