type-check

Enforce cross-language type-safety rules across TypeScript, Python, Go, Rust, and JavaScript.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill type-check-mikecubed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: type-check
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/ccc/skills/type-check
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill type-check-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill enforces cross-language type-safety rules to prevent common typing issues across multiple languages.

Core Features & Use Cases

  • Applies TYPE-1 through TYPE-6 checks across TypeScript, Python, Go, Rust, and JavaScript.
  • Loads language-specific references to guide applicability and tooling recommendations.
  • Integrates with conductor workflows to surface actionable type-safety violations in code reviews.

Quick Start

Run the type-check workflow against your codebase to surface and fix type-safety violations.

Frequently Asked Questions about type-check

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

FAQPage Schema
How do I enforce type-safety rules across TypeScript, Python, Go, and Rust codebases?

Cross-language type-safety rules are enforced by evaluating TYPE-1 through TYPE-6 checks against your code to catch escape-hatch types, unsafe casts, and non-exhaustive pattern matching with actionable citations.

How do I catch unsafe casts and escape-hatch types during code review?

Unsafe casts and escape-hatch types are caught by integrating type-check into conductor workflows, which surfaces type-safety violations during code write and review using loaded language-specific references.

Does this type-check tool support static analysis for JavaScript projects?

Yes, static analysis for JavaScript projects is fully supported alongside TypeScript, Python, Go, and Rust, applying standardized type-safety checks to identify typing issues.

What is non-exhaustive pattern matching and how do I identify it in my code?

Non-exhaustive pattern matching is a type-safety violation identified by evaluating your code against language-specific references, ensuring all possible cases are handled to prevent runtime errors.

Can I integrate static type analysis into automated code review workflows?

Yes, static type analysis integrates into conductor workflows and automated reviews, loading language references to surface actionable type-safety violations directly in your review process.

What are the limitations of cross-language type checking for polyglot repositories?

Cross-language type checking is limited to supported languages—TypeScript, Python, Go, Rust, and JavaScript—and focuses strictly on type-safety rules, requiring language-specific references for accurate guidance.