ts-project-health

Run universal and TypeScript-specific checks to produce a unified health report.

1|5|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mdproctor/cc-praxis --skill ts-project-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ts-project-health
Source: https://github.com/mdproctor/cc-praxis/tree/main/ts-project-health
Command: npx skills add https://github.com/mdproctor/cc-praxis --skill ts-project-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript and Node.js projects often accumulate health issues between sessions. This skill provides a structured health review by running universal checks from project-health and adding TypeScript-specific categories to surface type-safety, build integrity, dependency health, and test coverage gaps.

Core Features & Use Cases

  • Inherits universal checks from project-health and adds TS-specific categories (ts-types, ts-async, ts-build, ts-dependencies, ts-testing).
  • Produces a unified health report across a TS project to guide improvements in type safety, async patterns, dependencies, and tests.
  • Use Case: run this before releases or PRs to ensure TypeScript projects meet quality standards and reduce surprises in CI.

Quick Start

Run /ts-project-health to perform a full health check on your TypeScript/Node.js project.

Frequently Asked Questions about ts-project-health

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

FAQPage Schema
How do I run a health check on my TypeScript project?

To run a TypeScript project health check, execute a single command that combines universal code quality checks with TS-specific categories like type-safety, async patterns, build integrity, and test coverage to generate a unified health report.

What does a TypeScript code quality check include?

A TypeScript code quality check includes universal lint and testing standards alongside TS-specific categories: ts-types, ts-async, ts-build, ts-dependencies, and ts-testing, ensuring type safety and build reliability across Node.js projects.

Can I use this health check on an existing Node.js codebase?

Yes, this health check applies to both new and existing TypeScript and Node.js codebases, identifying accumulated health issues to improve code quality, reliability, and maintainability across the project.

When should I check my TypeScript project for health issues?

You should check TypeScript project health before releases or pull requests to ensure code meets quality standards, reducing unexpected CI failures and surfacing type-safety or dependency gaps early.

What's the best way to find type-safety and build issues in TS projects?

The best way to find type-safety and build issues is running a structured health review that executes universal checks prior to TS-specific checks, presenting results in a unified format to guide targeted improvements.

Why does my TypeScript project health check run universal checks first?

Universal checks run first to establish a baseline of standard code quality and lint issues before layering TS-specific checks for type-safety, async patterns, and build integrity, ensuring a logically structured and unified health report.