pi-agent-rust
Speeds up pi_agent_rust development and verification workflows. Use when editing providers, tools, sessions, extensions, installer/uninstaller logic, or triaging regressions in this repo.
How do I install this agent skill?
npx skills add https://github.com/evolv3-ai/vibe-skills --skill pi-agent-rustIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill facilitates development and testing for a Rust-based project by providing standard commands for compilation, linting, and regression testing. No security threats or malicious behaviors were detected.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Pi Agent Rust
60-Second Bootstrap
export CARGO_TARGET_DIR="/data/tmp/pi_agent_rust/${USER:-agent}"
export TMPDIR="/data/tmp/pi_agent_rust/${USER:-agent}/tmp"
mkdir -p "$TMPDIR"
rch exec -- cargo check --all-targets
rch exec -- cargo clippy --all-targets -- -D warnings
cargo fmt --check
bash tests/installer_regression.sh
Symptom Router
| Symptom | First 3 Commands |
|---|---|
| Provider stream/tool-call regression | cargo test provider_streaming -- --nocapture ; `rg -n "stream |
| Session replay/index drift | cargo test session -- --nocapture ; `rg -n "Session |
| Extension policy/runtime failure | cargo test extension -- --nocapture ; `rg -n "policy |
| Installer/uninstaller/skill issue | bash tests/installer_regression.sh ; `rg -n "AGENT_SKILL_STATUS |
| Interactive vs RPC divergence | cargo test e2e_rpc -- --nocapture ; `rg -n "interactive |
For deeper diagnosis, use references/DEBUGGING-PLAYBOOKS.md.
Non-Negotiables
- Read
AGENTS.mdfirst, then follow it exactly. - Do not delete files or run destructive git/filesystem commands.
- Keep edits in-place; avoid creating variant files for the same purpose.
- Use
mainsemantics in docs/scripts; do not introducemaster. - Prefer
rgfor fast text recon andast-grepfor structural matching/refactors. - Prefer
rch exec -- <cargo ...>for heavy compile/test workloads. - After substantive edits, run compile/lint/format gates and the smallest relevant regression slice.
Core Workflow
- Recon: identify exact change surface and invariants.
- Implement: minimal, behavior-focused patch with explicit failure semantics.
- Validate: targeted tests first, broaden only as needed.
- Verify UX: error/status output is explicit, stable, and non-ambiguous.
- Sync docs: update
README.mdwhen flags/behavior/user guidance changed.
Changed Files -> Required Tests
| Changed Files (examples) | Minimum Required Tests |
|---|---|
install.sh, uninstall.sh, .claude/skills/pi-agent-rust/** | bash -n install.sh uninstall.sh tests/installer_regression.sh ; shellcheck -x install.sh uninstall.sh tests/installer_regression.sh ; bash tests/installer_regression.sh ; bash scripts/skill-smoke.sh |
src/providers/**, src/provider.rs, src/sse.rs | cargo test provider_streaming ; cargo test conformance |
src/session.rs, src/session_index.rs, src/session_test.rs | cargo test session ; cargo test conformance |
src/extensions.rs, src/extensions_js.rs | cargo test extension ; cargo test conformance |
src/tools.rs | cargo test tools ; cargo test conformance |
src/interactive.rs, src/rpc.rs, src/main.rs | cargo test e2e_rpc ; cargo test conformance |
Do Not Run Yet
Run these only after targeted repro + focused slice indicates need:
- Broad
cargo testacross entire workspace when a narrower slice already reproduces. - Heavy multi-surface runs before confirming changed-file impact.
- Repeated full conformance loops while the core failing slice is still unstable.
High-Value Commands
# Fast recon
git status --short
rg -n "install|uninstall|skill|checksum|sigstore|completion|provider|session|extension" \
install.sh uninstall.sh README.md tests/installer_regression.sh src/
# Installer + skill safety gates
bash -n install.sh uninstall.sh tests/installer_regression.sh
shellcheck -x install.sh uninstall.sh tests/installer_regression.sh
bash tests/installer_regression.sh
bash scripts/skill-smoke.sh
# Rust gates
rch exec -- cargo check --all-targets
rch exec -- cargo clippy --all-targets -- -D warnings
cargo fmt --check
For an expanded command cookbook, see references/COMMANDS.md.
For deep incident triage, see references/DEBUGGING-PLAYBOOKS.md.
Critical Files
src/main.rs: CLI entry and mode dispatch.src/agent.rs: agent loop and tool iteration behavior.src/provider.rs: provider trait contract.src/providers/: provider implementations and factory wiring.src/tools.rs: built-in tools (read,write,edit,bash,grep,find,ls).src/session.rs: JSONL session persistence.src/session_index.rs: session index and metadata cache.src/extensions.rs+src/extensions_js.rs: extension policy and QuickJS bridge.src/interactive.rs+src/rpc.rs: TUI and RPC/stdin surfaces.install.sh+uninstall.sh: install lifecycle, migration, and skill management.tests/installer_regression.sh: installer regression harness.scripts/skill-smoke.sh: skill integrity + inline-sync validation.
Known Footguns
- Custom artifact install paths without compatible release context can fall back incorrectly if not explicitly guarded.
- Skill status can become misleading on mixed outcomes unless partial/failure branches are explicit.
- Uninstall logic must enforce both marker checks and expected destination path shape.
- Installer progress/status text should stay on stderr when stdout is used for data plumbing.
- Bundled skill and inline fallback can silently drift unless explicitly checked.
Patch Patterns
Pattern 1: Mixed Outcome Status Clarity
# BEFORE: everything collapsed into "skipped custom"
if [ "$skipped_custom" -ge 1 ]; then
AGENT_SKILL_STATUS="skipped (existing custom skill)"
fi
# AFTER: distinguish custom-skip from write failure
if [ "$skipped_custom" -ge 1 ] && [ "$failed_writes" -ge 1 ]; then
AGENT_SKILL_STATUS="partial (custom skill kept; other install failed)"
elif [ "$skipped_custom" -ge 1 ]; then
AGENT_SKILL_STATUS="skipped (existing custom skill)"
fi
Pattern 2: Safe Skill Replacement
# BEFORE: remove destination before validating copy result
rm -rf "$destination"
cp "$source" "$destination/SKILL.md"
# AFTER: stage then atomically move into place
staged="$(mktemp -d ...)"
cp "$source" "$staged/SKILL.md"
mv "$staged" "$destination"
Failure Triage
- Installer summary/status mismatch:
trace
AGENT_SKILL_STATUS,CHECKSUM_STATUS, andCOMPLETIONS_STATUSininstall.sh. - Install/uninstall safety concern: verify marker checks and expected destination guards in both scripts.
- Provider/session/extension regressions:
use symptom router, then follow
references/DEBUGGING-PLAYBOOKS.md. - Docs drift:
ensure
README.mdflags/examples match current installer behavior.
Done Criteria
- Changed-file matrix minimum tests passed.
- Compile/lint/format checks passed for touched surfaces.
- Installer/skill changes pass
tests/installer_regression.shandscripts/skill-smoke.sh. - Behavior is explicit on failure paths; no silent fallback surprises.
- Skill docs and inline fallback remain aligned and current.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/evolv3-ai/vibe-skills/pi-agent-rust">View pi-agent-rust on skillZs</a>