Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

typecheck

Estrellas2

Forks0

Actualizado9 de febrero de 2026 a las 11:38

Run TypeScript type checking across the entire monorepo

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

threahq

threahq/threa

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	typecheck
description	Run TypeScript type checking across the entire monorepo
allowed-tools	Bash(bun run typecheck:), Bash(bun run --cwd:)

Typecheck

Runs TypeScript type checking across the entire monorepo. Reports errors with file locations and suggests fixes.

Instructions

Step 1: Run Typecheck

Run the root typecheck command which checks all workspaces in dependency order:

bun run typecheck 2>&1

This runs tsc --noEmit across:

packages/types — shared domain types (no dependencies)
packages/prosemirror — editor state wrapper (depends on types)
apps/backend — Express API + Workers + Evals (depends on types, prosemirror)
apps/frontend — React app (depends on types)

Step 2: Report Results

If all workspaces pass (exit code 0):

Typecheck passed — all 4 workspaces clean.

If errors are found (exit code non-zero):

Parse errors from the output. TypeScript errors follow the format: path/file.ts(line,col): error TSXXXX: message
Group errors by workspace and file
For each error, read the relevant file around the error line to understand context
Report errors grouped by workspace:

Typecheck found N errors in M files:

**packages/types** (0 errors)
**packages/prosemirror** (0 errors)
**apps/backend** (X errors)
  - `src/path/file.ts:42` — TS2345: description + suggested fix
  - `evals/path/file.ts:10` — TS6133: description + suggested fix

**apps/frontend** (Y errors)
  - `src/path/file.ts:100` — TS2322: description + suggested fix

If the user wants fixes, apply them. Common patterns:
- TS6133 (unused variable): Remove the variable or prefix with _ (only in backend — frontend has noUnusedLocals: true which doesn't respect _ prefix)
- TS2345 (type mismatch): Check if a type changed upstream and update the usage
- TS2307 (cannot find module): Check if a file was moved and update the import path
- TS2322 (type not assignable): Check if a constant/enum value changed

Step 3: Targeted Workspace Check (Optional)

If the user specifies a workspace, run only that one:

bun run --cwd packages/types typecheck 2>&1
bun run --cwd packages/prosemirror typecheck 2>&1
bun run --cwd apps/backend typecheck 2>&1
bun run --cwd apps/frontend typecheck 2>&1

Notes

Backend tsconfig includes src/**/* and evals/**/* — both application code and eval suites are type-checked
The workspaces run sequentially because they have dependency relationships
Frontend has noUnusedLocals: true and noUnusedParameters: true — stricter than backend

Example Usage

/typecheck
/typecheck backend
/typecheck frontend

Más de este repositorio

mismo repositorio

update-pi-remote-plugin

threahq/threa

Keep the Threa Pi remote-control extension in `extensions/pi-remote/` aligned with the current Pi extension API and Threa bot-runtime public API. Use when asked to update, verify, sync, or troubleshoot the Pi remote plugin, `/remote-control`, or `threa-remote.ts`.

2026-07-052

create-pr

threahq/threa

Create a well-structured pull request with proper description, design decisions, and file changes. Use when asked to create a PR, open a PR, or submit changes for review.

2026-07-032

threa-public-api

threahq/threa

Call Threa's public REST API (send/list/search/update/delete messages, list streams/users/members, search memos/attachments) with curl or a Bun script. Use when asked to post messages to a stream, seed a stream with test data, drive the API from automation, dedupe by metadata, inspect a production workspace (streams, messages, members) for troubleshooting, or otherwise hit https://staging.threa.io / https://app.threa.io endpoints with an API key. Reads from production should use the read-only prod key.

2026-06-202

deslopify

threahq/threa

Rewrite user-facing copy (marketing pages, docs, headings, UI microcopy, READMEs, PR descriptions) to strip AI-slop and salesy tone, leaving plain, understated, factual prose. Use when asked to "deslopify", "deslop", "remove the AI slop", "make this less salesy/less AI-sounding", "make the copy plainer", or when reviewing copy for slop tells.

2026-06-162

code-review

threahq/threa

Run multi-perspective code review on a PR or the local branch

2026-06-152

handover

threahq/threa

Write a session handover doc for the next agent picking up this line of work. Use when asked to "write a handover", "hand over", "handoff doc", or at the end of a session whose work continues in a future session.

2026-06-122

name	typecheck
description	Run TypeScript type checking across the entire monorepo
allowed-tools	Bash(bun run typecheck:), Bash(bun run --cwd:)

Typecheck

Runs TypeScript type checking across the entire monorepo. Reports errors with file locations and suggests fixes.

Instructions

Step 1: Run Typecheck

Run the root typecheck command which checks all workspaces in dependency order:

bun run typecheck 2>&1

This runs tsc --noEmit across:

packages/types — shared domain types (no dependencies)
packages/prosemirror — editor state wrapper (depends on types)
apps/backend — Express API + Workers + Evals (depends on types, prosemirror)
apps/frontend — React app (depends on types)

Step 2: Report Results

If all workspaces pass (exit code 0):

Typecheck passed — all 4 workspaces clean.

If errors are found (exit code non-zero):

Parse errors from the output. TypeScript errors follow the format: path/file.ts(line,col): error TSXXXX: message
Group errors by workspace and file
For each error, read the relevant file around the error line to understand context
Report errors grouped by workspace:

Typecheck found N errors in M files:

**packages/types** (0 errors)
**packages/prosemirror** (0 errors)
**apps/backend** (X errors)
  - `src/path/file.ts:42` — TS2345: description + suggested fix
  - `evals/path/file.ts:10` — TS6133: description + suggested fix

**apps/frontend** (Y errors)
  - `src/path/file.ts:100` — TS2322: description + suggested fix

If the user wants fixes, apply them. Common patterns:
- TS6133 (unused variable): Remove the variable or prefix with _ (only in backend — frontend has noUnusedLocals: true which doesn't respect _ prefix)
- TS2345 (type mismatch): Check if a type changed upstream and update the usage
- TS2307 (cannot find module): Check if a file was moved and update the import path
- TS2322 (type not assignable): Check if a constant/enum value changed

Step 3: Targeted Workspace Check (Optional)

If the user specifies a workspace, run only that one:

bun run --cwd packages/types typecheck 2>&1
bun run --cwd packages/prosemirror typecheck 2>&1
bun run --cwd apps/backend typecheck 2>&1
bun run --cwd apps/frontend typecheck 2>&1

Notes

Backend tsconfig includes src/**/* and evals/**/* — both application code and eval suites are type-checked
The workspaces run sequentially because they have dependency relationships
Frontend has noUnusedLocals: true and noUnusedParameters: true — stricter than backend

Example Usage

/typecheck
/typecheck backend
/typecheck frontend