tyche-test-and-verify

Runs typecheck, test, lint, build, and devnet verification for the tyche monorepo.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/IagoPrandi/ai-dealer --skill tyche-test-and-verify-iagoprandi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tyche-test-and-verify
Source: https://github.com/IagoPrandi/ai-dealer/tree/main/.claude/skills/tyche-test-and-verify
Command: npx skills add https://github.com/IagoPrandi/ai-dealer --skill tyche-test-and-verify-iagoprandi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It prevents developers from claiming work is done based on incomplete checks by enforcing a strict verification ladder across the tyche monorepo's TypeScript apps and Rust Solana program, including live devnet reconciliation. ## Core Features & Use Cases - Per-package verification ladder: Runs typecheck, test, lint (with --max-warnings=0), and build in order for every touched package, including shared rule packages. - Rust/SBF contract testing via Docker: Executes cargo checks, dual-feature clippy, and single-threaded SBF instruction tests inside a pinned toolchain container. - Live devnet verification: Guides dry-run-then-broadcast settlement, claims, and input seeding with on-chain, API, and audit reconciliation plus idempotency checks. - Use Case: After fixing a settlement bug in apps/worker, use this Skill to run the full ladder, rebuild the SBF program, dry-run the settlement runner, broadcast, and confirm the re-run is a no-op. ## Quick Start Verify my changes to apps/worker and the Solana program correctly before marking anything done.

Frequently Asked Questions about tyche-test-and-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run tests in a pnpm monorepo per package?▼

Run pnpm --filter @tyche/<pkg> followed by typecheck, test, lint, and build in that order, requiring each step green before the next. Tests use node --test with tsx and co-located *.test.ts files importing from node:test and node:assert/strict.

How to test a Solana Rust program without anchor installed locally?▼

Run all contract work inside a pinned rust:1.91-bookworm Docker container via scripts/run-cargo.mjs, mounting a volume for the toolchain and deploy keypairs. SBF instruction tests run with --test-threads=1 because they are flaky in parallel.

Why does clippy need to run with both feature sets?▼

Code gated by #[cfg(feature=...)] is only checked under the matching feature set, so the default build misses devnet-test branches and --all-features misses the production cfg(not(...)) branch. Both clippy runs are required for full coverage.

Why does my Docker container run stale code after editing source files?▼

tsx watch does not hot-reload over Windows bind mounts, so the container keeps old code until you run docker compose restart. One-off docker exec tsx invocations do read current source since tsx recompiles each run.

How do I verify an on-chain Solana error without broadcasting?▼

Use a read-only simulateTransaction with sigVerify false and replaceRecentBlockhash true to reproduce the failure as any wallet. The simulation logs print the Error Code and Error Number without requiring a signature or broadcast.

What makes a devnet settlement fully verified?▼

All three stores must agree: on-chain TurnState and Claim PDAs, API projections like GET /rounds and verification results, and the hash-linked audit chain with integrity true. Re-running the broadcast must be a no-op returning already_closed.