القائمة
Run TypeScript type checking across the entire monorepo
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | typecheck |
| description | Run TypeScript type checking across the entire monorepo |
| allowed-tools | Bash(bun run typecheck:*), Bash(bun run --cwd:*) |
Runs TypeScript type checking across the entire monorepo. Reports errors with file locations and suggests fixes.
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)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
_ (only in backend — frontend has noUnusedLocals: true which doesn't respect _ prefix)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
src/**/* and evals/**/* — both application code and eval suites are type-checkednoUnusedLocals: true and noUnusedParameters: true — stricter than backend/typecheck
/typecheck backend
/typecheck frontend
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`.
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.
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.
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.
Run multi-perspective code review on a PR or the local branch
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.