Run any Skill in Manus with one click

tsz-conformance

Stars443

Forks8

UpdatedJune 2, 2026 at 05:23

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mohsen1

mohsen1/tsz

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	tsz-conformance
description	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.

TSZ Conformance

Conformance is a regression gate. Prefer checked-in artifacts and narrow filters; CI owns broad runs.

Rules

Read AGENTS.md and docs/plan/ROADMAP.md for conformance-affecting work.
Do not run full conformance locally.
Treat a failing test as a witness for a structural rule.
Do not hide regressions with snapshot/allowlist churn.

Offline First

python3 scripts/conformance/query-conformance.py --dashboard
python3 scripts/conformance/query-conformance.py --campaigns
python3 scripts/conformance/query-conformance.py --fingerprint-only
python3 scripts/conformance/query-conformance.py --code TS2322
python3 scripts/conformance/query-conformance.py --code TS2322 --paths-only

Artifacts: conformance-detail.json, conformance-snapshot.json, conformance-accepted-regressions.txt, conformance-shard-weights.json.

Focused Run

./scripts/conformance/conformance.sh run --filter "<name>" --verbose

Keep filters precise. Let harnesses rebuild stale binaries when possible.

Triage

Classify: new/accepted/resolved/fingerprint-only/wrong-code/missing-code/ extra-code/crash/timeout/OOM. Then identify owner: relation, inference, narrowing, indexed/keyof/mapped/conditional/template, symbol resolution, diagnostic display, parser recovery, or emit-only.

Before coding, state the structural rule and adjacent cases. Behavior changes need owning-crate tests.

Accepted-regression drift: verify shard artifacts, update the accepted file only to match observed failing set, link/file issues for new accepts, and comment with numbers plus AgentName.

More from this repository

same repository

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-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

tsz-pr-coordination

mohsen1/tsz

Create, refresh, and publish TSZ pull requests with correct coordination state. Use when opening a draft PR, updating a PR body, applying canonical agent labels, changing WIP/draft/ready state, acknowledging review, handing off readiness to a manager agent, or making sure a TSZ PR satisfies AgentName, Project Corpus Impact, verification, and overlap rules.

2026-06-02443

name	tsz-conformance
description	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.

TSZ Conformance

Conformance is a regression gate. Prefer checked-in artifacts and narrow filters; CI owns broad runs.

Rules

Read AGENTS.md and docs/plan/ROADMAP.md for conformance-affecting work.
Do not run full conformance locally.
Treat a failing test as a witness for a structural rule.
Do not hide regressions with snapshot/allowlist churn.

Offline First

python3 scripts/conformance/query-conformance.py --dashboard
python3 scripts/conformance/query-conformance.py --campaigns
python3 scripts/conformance/query-conformance.py --fingerprint-only
python3 scripts/conformance/query-conformance.py --code TS2322
python3 scripts/conformance/query-conformance.py --code TS2322 --paths-only

Artifacts: conformance-detail.json, conformance-snapshot.json, conformance-accepted-regressions.txt, conformance-shard-weights.json.

Focused Run

./scripts/conformance/conformance.sh run --filter "<name>" --verbose

Keep filters precise. Let harnesses rebuild stale binaries when possible.

Triage

Before coding, state the structural rule and adjacent cases. Behavior changes need owning-crate tests.

Accepted-regression drift: verify shard artifacts, update the accepted file only to match observed failing set, link/file issues for new accepts, and comment with numbers plus AgentName.