菜单
Use this skill in ametel01 TypeScript repos and packages that use Bun, Biome, Prettier, strict tsconfig, Vitest or Bun test, Next.js, Hono, Apibara, or workspace scripts. It guides installs, lint/format/typecheck/build commands, TypeScript invariants, and known formatting variants.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use this skill when adding or fixing orgs-ai-harness tests, validation rules, generated artifact schema checks, or local quality commands for the Python unittest suite.
Use this skill when changing draft approval, protected artifact metadata, eval replay, verification thresholds, repo-local cache refresh, export policy, or explain output.
Use this skill when modifying GitHub repository discovery, `gh repo list` integration, explicit repo selection, fork/archive filters, clone behavior, or interactive checkbox selection.
Use this skill when changing orgs-ai-harness CLI commands, setup wizard flows, argparse subcommands, user-facing command output, or command error handling in `src/orgs_ai_harness/cli.py`.
Use this skill when editing `harness.yml` parsing, repo registry mutations, org pack initialization, repo coverage statuses, or config round-trip behavior in orgs-ai-harness.
Use this skill when adding or fixing orgs-ai-harness tests, validation rules, generated artifact schema checks, or local quality commands for the Python unittest suite.
基于 SOC 职业分类
| name | bun-typescript-quality |
| description | Use this skill in ametel01 TypeScript repos and packages that use Bun, Biome, Prettier, strict tsconfig, Vitest or Bun test, Next.js, Hono, Apibara, or workspace scripts. It guides installs, lint/format/typecheck/build commands, TypeScript invariants, and known formatting variants. |
Keep TypeScript changes aligned with the account's Bun-first repos while detecting package-local variants.
Use when editing .ts, .tsx, package.json, tsconfig.json, Biome/Prettier config, Next.js frontend code, Hono server code, or Apibara indexer code in sampled repos.
Strength: Strong.
vitals-db: Bun workspace root with bun.lock, biome.json, project references, bun run verify.agent-vitals: Bun package with bun.lock, Biome linting, Prettier formatting, strict tsconfig.json.horizon-starknet/packages/frontend: Bun, Next.js, Biome, strict TS, Playwright e2e.horizon-starknet/packages/indexer: Bun, Apibara, Biome, Vitest, strict TS, Docker helpers.package.json, bun.lock, biome.json, .prettierrc*, and tsconfig.json.bun install --frozen-lockfile only in the package or workspace root that owns the lockfile.vitals-db: bun run check:ci, bun run typecheck, bun run test, bun run build, or bun run verify.agent-vitals: bun run check, bun run build.horizon-starknet/packages/frontend: bun run check, bun run test, bun run build; use bun run test:e2e --project=chromium for e2e-impacting UI changes.horizon-starknet/packages/indexer: bun run check, bun run test, bun run build.strict, noUncheckedIndexedAccess, exactOptionalPropertyTypes, and unused-code checks intact where configured.import type/export type where Biome requires it.noExplicitAny, unused imports, and non-null assertion rules respected unless the local override already permits the case.agent-vitals disables Biome formatting and uses Prettier for formatting; do not use biome format there unless scripts change.vitals-db uses a root workspace and TypeScript project references; package-local changes can still require root bun run typecheck.horizon-starknet frontend and indexer use independent lockfiles and package scripts.biome.json before applying a rule globally.If a TypeScript repo lacks bun.lock, this skill is only a hint. Re-run org-toolchain-detection and follow the repo's own package manager.