원클릭으로 Manus에서 모든 스킬 실행

tsz-project-bench

스타443

포크8

업데이트2026년 6월 2일 05:23

Work on TSZ benchmark and project-corpus compatibility. Use when investigating bench.yml failures, project compile guard rows, benchmark dashboard data, PGO bench setup, fixture metadata drift, or real-project blockers such as utility-types, ts-toolbelt, ts-essentials, rxjs, type-fest, zod, kysely, Next, or Vite.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

mohsen1

mohsen1/tsz

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

TSZ Project Bench

Use for project-corpus rows, benchmark harness, fixture metadata, PGO bench setup, and website benchmark data.

Rules

Read AGENTS.md and docs/plan/ROADMAP.md for durable benchmark/project work.
Inspect overlapping PRs/issues.
Red row = correctness blocker before speed problem unless failure is runtime, residency, timeout, or OOM.
Keep fixture metadata shared across project-fixtures.sh, bench-vs-tsgo.sh, and project-compile-guard.sh.
Wrap long/heavy local commands with scripts/safe-run.sh.

Sources

scripts/bench/project-fixtures.sh
scripts/bench/bench-vs-tsgo.sh
scripts/ci/project-compile-guard.sh
crates/tsz-website/src/_data/benchmark_data.js
.github/workflows/bench.yml

Workflow

Identify row, phase, and first failure: prepare, tsc validation, tsz check, emit scope, crash, timeout, OOM, metadata, website ingestion, timing.
Required/canary/all set: TSZ_PROJECT_COMPILE_SET=<required|canary|all>.
Reproduce with the narrowest filter.
If typecheck fails, reduce to owning compiler operation before optimizing.
For speed work, name repeated operation and complexity change. No fixture-name special cases.

Commands

./scripts/bench/bench-vs-tsgo.sh --prepare-only
./scripts/bench/bench-vs-tsgo.sh --quick --filter "<row>" --json-file /tmp/bench.json
TSZ_PROJECT_COMPILE_FILTER="<row>" TSZ_PROJECT_COMPILE_SET=required scripts/ci/project-compile-guard.sh
TSZ_PROJECT_COMPILE_ALLOW_FAILURES=1 TSZ_PROJECT_COMPILE_SET=all scripts/ci/project-compile-guard.sh

PR notes: row, before/after failure class, first broken phase, owner layer, fixture metadata changes, whether timing is meaningful, commands/CI links, AgentName.

이 저장소의 다른 Skills

같은 저장소

tsz-architecture

mohsen1/tsz

Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code. Use when planning semantic fixes, moving logic across query boundaries, handling architecture guard failures, ratcheting boundary debt, or reviewing changes for solver-first and no hardcoding rules.

2026-06-02443

tsz-ci-pr

mohsen1/tsz

Drive TSZ GitHub PRs through review, CI, and the merge queue. Use when checking PR status, debugging failing GitHub Actions, deciding whether a PR is WIP, marking draft PRs ready, enqueueing or verifying the queue, landing a PR, or interpreting TSZ CI gates.

2026-06-02443

tsz-conformance

mohsen1/tsz

Triage and maintain TSZ diagnostic conformance. Use when investigating conformance regressions, accepted-regression drift, fingerprint-only failures, issue creation from conformance data, or focused parity fixes that must preserve the conformance gate.

2026-06-02443

tsz-disk-cache-hygiene

mohsen1/tsz

Prevent TSZ machines and worktrees from running out of disk while preserving useful build caches. Use before creating worktrees, running large builds/tests, diagnosing low disk, cleaning artifacts, deciding whether to delete caches, or recovering space without slowing future Rust/TypeScript builds.

2026-06-02443

tsz-iteration-audit

mohsen1/tsz

Audit TSZ repo iteration speed and quality. Use when asked to deep-dive repo health, identify avoidable delays, improve agent workflows, reduce CI/PR churn, add guardrails, choose skills to install or create, or turn recurring TSZ process failures into focused tooling/docs PRs.

2026-06-02443

tsz-performance-engineering

mohsen1/tsz

Use when planning, implementing, reviewing, or interpreting TSZ performance work, including benchmark regressions, cache/residency changes, timing claims, perf counters, hotspot investigations, OOM/timeout/stack-overflow blockers, or optimization PR evidence.

2026-06-02443

name	tsz-project-bench
description	Work on TSZ benchmark and project-corpus compatibility. Use when investigating bench.yml failures, project compile guard rows, benchmark dashboard data, PGO bench setup, fixture metadata drift, or real-project blockers such as utility-types, ts-toolbelt, ts-essentials, rxjs, type-fest, zod, kysely, Next, or Vite.

TSZ Project Bench

Use for project-corpus rows, benchmark harness, fixture metadata, PGO bench setup, and website benchmark data.

Rules

Read AGENTS.md and docs/plan/ROADMAP.md for durable benchmark/project work.
Inspect overlapping PRs/issues.
Red row = correctness blocker before speed problem unless failure is runtime, residency, timeout, or OOM.
Keep fixture metadata shared across project-fixtures.sh, bench-vs-tsgo.sh, and project-compile-guard.sh.
Wrap long/heavy local commands with scripts/safe-run.sh.

Sources

scripts/bench/project-fixtures.sh
scripts/bench/bench-vs-tsgo.sh
scripts/ci/project-compile-guard.sh
crates/tsz-website/src/_data/benchmark_data.js
.github/workflows/bench.yml

Workflow

Identify row, phase, and first failure: prepare, tsc validation, tsz check, emit scope, crash, timeout, OOM, metadata, website ingestion, timing.
Required/canary/all set: TSZ_PROJECT_COMPILE_SET=<required|canary|all>.
Reproduce with the narrowest filter.
If typecheck fails, reduce to owning compiler operation before optimizing.
For speed work, name repeated operation and complexity change. No fixture-name special cases.

Commands

./scripts/bench/bench-vs-tsgo.sh --prepare-only
./scripts/bench/bench-vs-tsgo.sh --quick --filter "<row>" --json-file /tmp/bench.json
TSZ_PROJECT_COMPILE_FILTER="<row>" TSZ_PROJECT_COMPILE_SET=required scripts/ci/project-compile-guard.sh
TSZ_PROJECT_COMPILE_ALLOW_FAILURES=1 TSZ_PROJECT_COMPILE_SET=all scripts/ci/project-compile-guard.sh

PR notes: row, before/after failure class, first broken phase, owner layer, fixture metadata changes, whether timing is meaningful, commands/CI links, AgentName.