source-command-fix-typescript

Fix TypeScript type errors within a monorepo project using turbo check-types.

Updated May 14, 2026
One-click install
npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-fix-typescript-chroniicallydiistracted
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-fix-typescript
Source: https://github.com/chroniicallydiistracted/LorcanaChamp/tree/main/references/lorcana-simulator/.agents/skills/source-command-fix-typescript
Command: npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-fix-typescript-chroniicallydiistracted

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps eliminate TypeScript type errors in a specific package within a monorepo by running the repo’s typecheck for the targeted project and iteratively applying fixes only inside that project.

Core Features & Use Cases

  • Targeted type diagnosis: Runs bunx turbo check-types --filter={packageName} and focuses only on errors originating from the designated {projectName}.
  • Iterative, within-scope fixes: Applies code changes strictly inside {projectName} to resolve each reported error (avoiding broad suppression like ts-ignore unless no in-scope fix exists).
  • Validation loop: Re-checks using bun run typecheck and repeats until bunx turbo check-types --filter=@lorcanito/{projectName} reports zero type errors for the targeted project.

Quick Start

Tell the agent: run the skill to fix TypeScript errors for the project {projectName} by executing the turbo typecheck for that package and iteratively patching only files within {projectName} until there are no remaining type errors.

Frequently Asked Questions about source-command-fix-typescript

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

FAQPage Schema
How do I fix TypeScript errors in a single package within a monorepo?

Fix TypeScript errors in a single package by running a filtered typecheck command like `bunx turbo check-types --filter={packageName}`, then iteratively applying code changes only within that project until zero type errors remain.

Why do my TypeScript type fixes in one monorepo package break typechecking in other packages?

TypeScript type fixes in one monorepo package can break others if changes leak outside the targeted scope. This Skill applies iterative code changes strictly within the designated package to resolve type errors without affecting other projects.

What's the best way to run a package-scoped TypeScript typecheck in a Turbo monorepo?

The best way to run a package-scoped TypeScript typecheck in a Turbo monorepo is executing `bunx turbo check-types --filter=@lorcanito/{projectName}` to validate only the targeted project, repeating the check until all type errors are resolved.

Can I use ts-ignore to resolve TypeScript errors when migrating types in a specific monorepo package?

Using `ts-ignore` to resolve TypeScript errors is avoided unless no in-scope fix exists. This Skill implements robust code fixes directly within the targeted package to deterministically clear type errors without broad suppressions.

Does this TypeScript type fixing workflow work with bun and Turbo for build validation?

Yes, this TypeScript type fixing workflow works with bun and Turbo for build validation by executing `bunx turbo check-types` for the filtered package and repeatedly validating with `bun run typecheck` until deterministic completion criteria are met.