// 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.
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.
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.
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.
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.
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.
Start TSZ work safely in a crowded multi-agent checkout. Use when beginning a TSZ task, resuming a goal, switching or creating branches/worktrees, recovering from a merged or stale branch, checking disk/cache state, reading lane goals, or deciding whether local dirty files belong to the requested work.
| 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. |
Use this skill to inspect conformance state without turning local work into a full-suite run. Conformance is a regression gate; use snapshots and targeted filters first, then let ready-review CI run the broad suite.
AGENTS.md and docs/plan/ROADMAP.md before conformance-affecting work.Prefer offline snapshot data:
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
Use raw artifacts when the query output is too aggregated:
scripts/conformance/conformance-detail.json for per-test expected/actual
diagnostics and fingerprints.scripts/conformance/conformance-snapshot.json for aggregate KPIs.scripts/conformance/conformance-accepted-regressions.txt for the current
accepted regression runway.scripts/conformance/conformance-shard-weights.json for shard balancing.Run one test or one family only when the offline data is insufficient:
./scripts/conformance/conformance.sh run --filter "recursiveConditionalTypes" --verbose
Keep the filter precise. If the TypeScript submodule or dist binary is stale, prefer the harness rebuild path over manual broad rebuilds.
When <structural condition>, tsc does X; tsz should do X through <owner>.When CI aggregate reports both unlisted regressions and accepted regressions that no longer fail:
scripts/conformance/conformance-accepted-regressions.txt only to
make the accepted set match the observed failing set.AgentName.For conformance issues, include:
AgentName.