project-checker

HIRO15254's avatarfrom HIRO15254

Validate and fix code by running tsc, linting, and tests sequentially.

0stars🔀0forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Project Checker is a comprehensive quality assurance skill designed to automate the validation and repair of TypeScript projects. It executes a rigorous, sequential workflow—comprising type checking, linting, and unit testing—to ensure code integrity. Beyond simple detection, it empowers the AI agent to proactively resolve errors and re-verify fixes, maintaining a high standard of code health and stability.

Use Cases

  • Pre-deployment Validation: Automatically run a full suite of checks to ensure the codebase is error-free and meets quality standards before merging or deploying code.
  • Automated Debugging and Refactoring: Use the skill to identify and fix type regressions and logic errors immediately after large-scale code changes or refactoring sessions.
  • CI/CD Pipeline Simulation: Locally replicate the rigorous checks performed in professional CI/CD environments to catch and resolve issues before they reach the build server.
  • Codebase Health Maintenance: Periodically audit the entire project to clean up linting inconsistencies and ensure all tests remain passing as dependencies evolve.
nameproject-checker
descriptionValidate and fix code by running tsc, linting, and tests sequentially.

Project Checker

Validate the entire project and fix any errors found.

Instructions

Run the following commands in order, fixing any errors before proceeding:

1. TypeScript Type Check

tsc --noEmit

If type errors occur:

  • Read the affected files
  • Fix type definition issues
  • Re-run to verify the fix

2. Code Quality Check

bun run check:unsafe

If lint/format errors occur:

  • Review ESLint/Prettier errors
  • Fix code style issues
  • Re-run to verify the fix

3. Run Tests

bun run test

If tests fail:

  • Identify the failing test cases
  • Analyze whether the test or implementation is incorrect
  • Apply the appropriate fix
  • Re-run to verify the fix

Important

  • Continue fixing until each step passes without errors
  • Always re-verify after making fixes
  • Do not mark as complete until all checks pass
  • Report all fixes made to the user