check-and-fix

macalinao's avatarfrom macalinao

Run TypeScript checks and fix all errors (project)

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Debugging]

When & Why to Use This Skill

This Claude skill automates the end-to-end process of identifying, analyzing, and fixing TypeScript and linting errors within a project. By leveraging tools like Bash and intelligent file editing, it performs comprehensive type checks, applies automated linting fixes, and manually resolves complex code issues to ensure project stability and code quality.

Use Cases

  • Automated Error Resolution: Efficiently identify and fix a high volume of TypeScript type errors and syntax issues across an entire repository.
  • Pre-deployment Code Cleanup: Ensure a codebase is production-ready by resolving all linting warnings and type mismatches before merging pull requests.
  • Legacy Code Migration: Streamline the process of upgrading TypeScript versions or migrating JavaScript files by automatically handling resulting type inconsistencies.
  • Continuous Quality Assurance: Maintain project integrity by automatically verifying that all code fixes pass existing test suites and meet defined coding standards.
namecheck-and-fix
descriptionRun TypeScript checks and fix all errors (project)
modelsonnet
toolsBash, Edit, Read, Glob, Grep

Run the following commands in parallel to identify and fix errors:

  1. Run bun run typecheck to identify TypeScript errors
  2. Run bun run lint:fix to identify and automatically fix linting errors

Then fix remaining errors:

  1. Fix each TypeScript error found by:
    • Reading the affected files
    • Understanding the error context
    • Making the necessary code changes to resolve the errors
  2. If there are any remaining linting errors that couldn't be auto-fixed, manually fix them
  3. Run both bun run typecheck and bun run lint:fix again to verify all errors are resolved. IF THE ERRORS ARE NOT RESOLVED, REPEAT THE ENTIRE PROCESS.
  4. Run bun run test in the root to ensure no tests were broken.
  5. Provide a summary of what was fixed

Be thorough and ensure all errors are resolved and tests pass before completing the task.