pi-agent-rust
Made by JeffSpeeds up pi_agent_rust development and verification workflows. Use when editing providers, tools, sessions, extensions, installer/uninstaller logic, or triaging regressions in this repo.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
1Updates, enhancements, and release notes for this skill.
New: pi_agent_rust Skill, the fastest path to safe, verified edits in this Rust repo
An in-repo skill for the pi_agent_rust codebase. Symptom-first debugging playbooks, a 60-second bootstrap that runs cargo check, clippy, fmt, and the installer regression suite, and a critical-files map for providers, tools, sessions, extensions, and installer logic so an agent landing in the repo doesn't have to discover them from scratch.
- 60-second bootstrap that runs cargo check, clippy, fmt --check, and the installer regression suite in one block
- Per-user CARGO_TARGET_DIR and TMPDIR so multiple agents on the same dev box don't trample each other's build artifacts
- Symptom router with first-three-commands for five named symptoms: provider streaming, session replay drift, extension policy, installer/skill issues, interactive vs RPC divergence
- Changed-files matrix: each surface (providers, sessions, extensions, tools, RPC, installer) maps to its minimum required tests, usually a targeted slice plus cargo test conformance
- Heavy cargo check, clippy, and test runs go through rch exec; broad workspace test runs wait until a narrow slice reproduces the problem
The bootstrap is mechanical: set CARGO_TARGET_DIR and TMPDIR to a per-user scratch path, then run rch exec -- cargo check --all-targets, rch exec -- cargo clippy --all-targets -- -D warnings, cargo fmt --check, and bash tests/installer_regression.sh.
The symptom router is the core: five named symptoms (provider stream/tool-call regression, session replay/index drift, extension policy/runtime failure, installer/uninstaller/skill issues, interactive vs RPC divergence), each with the first three commands to run. A changed-files matrix names the minimum tests for each surface, and a "