rust-simplify
- Repo stars 0
- Author repo skills-registry
Rust Simplify
Use this skill for bounded Rust cleanup work in the Citum workspace when the task is to improve code quality rather than fix a specific bug.
When .jj is present, use docs/guides/JJ_AI_CHANGE_STACK.md for optional
local change isolation and intent capture before publishing through Git/GitHub.
Read first:
docs/guides/CODING_STANDARDS.mddocs/guides/AGENT_SKILLS.md
Target Selection
- Prefer
jcodemunchsymbol and file analysis before reading large files. - Pick the highest-value Rust file in the affected crate or module.
- If a file path was supplied, confirm it is actually wired into the build.
Quality Pass
- Reduce duplication and nested control flow.
- Prefer idiomatic Rust and explicit error handling.
- Review suspicious string ownership patterns. Prefer borrowed
&strfor lookup and comparison work, and allocateStringvalues at real ownership boundaries. - Do not perform broad allocation churn in hot paths without benchmark evidence.
- Add or update tests when behavior changes.
- When tests change, keep expected values independent of current implementation output and confirm behavior changes would have failed before the fix when practical.
- Keep the scope to one focused file or one tightly related cluster.
Verification
- Run the repo-required Rust checks for any
.rs,Cargo.toml, orCargo.lockchange. - Run
python3 scripts/audit-rust-review-smells.py --changedfor Rust cleanup passes and review the advisory findings. - Regenerate schemas if the touched files require it.
- Report the exact checks you ran and the result.
<!-- tomevault:4.0:skill_md:2026-05-23 -->Source: citum/citum-core — distributed by TomeVault.
- Fluxly category
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @tomevault-io · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Plug-and-play
- External API key
- No requirement detected
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Detected network behavior
- Local-only
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example.Prefer jcodemunch symbol and file analysis before reading large files. Pick the highest-value Rust file in the affected crate or module. If a file path was supplied, confirm it is actually wired into the build.
Reduce duplication and nested control flow. Prefer idiomatic Rust and explicit error handling. Review suspicious string ownership patterns. Prefer borrowed &str for lookup
Run the repo-required Rust checks for any .rs, Cargo.toml, or Cargo.lock change. Run python3 scripts/audit-rust-review-smells.py --changed for Rust cleanup passes and review the advisory findings.
# Rust Simplify
Use this skill for bounded Rust cleanup work in the Citum workspace when the task is to
improve code quality rather than fix a specific bug.
When `.jj` is present, use `docs/guides/JJ_AI_CHANGE_STACK.md` for optional
local change isolation and intent capture before publishing through Git/GitHub.
Read first:
- `docs/guides/CODING_STANDARDS.md`
- `docs/guides/AGENT_SKILLS.md`
## Target Selection
- Prefer `jcodemunch` symbol and file analysis before reading large files.
- Pick the highest-value Rust file in the affected crate or module.
- If a file path was supplied, confirm it is actually wired into the build.
## Quality Pass
- Reduce duplication and nested control flow.
- Prefer idiomatic Rust and explicit error handling.
- Review suspicious string ownership patterns. Prefer borrowed `&str` for lookup
and comparison work, and allocate `String` values at real ownership boundaries.
- Do not perform broad allocation churn in hot paths without benchmark evidence.
- Add or update tests when behavior changes.
- When tests change, keep expected values independent of current implementation
output and confirm behavior changes would have failed before the fix when
practical.
- Keep the scope to one focused file or one tightly related cluster.
## Verification
- Run the repo-required Rust checks for any `.rs`, `Cargo.toml`, or `Cargo.lock` change.
- Run `python3 scripts/audit-rust-review-smells.py --changed` for Rust cleanup
passes and review the advisory findings.
- Regenerate schemas if the touched files require it.
- Report the exact checks you ran and the result.
---
> Source: [citum/citum-core](https://github.com/citum/citum-core) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Target Selection → Quality Pass → Verification
terms -> Use this skill for bounded Rust cleanup work in the Citum workspace when the task is to improve code quality rather than fix a specific bug. · - Prefer jcodemunch symbol and file analysis before reading large files. · - Reduce duplication and nested control flow. · - Run the repo-required Rust checks for any .rs, Cargo.toml, or Cargo.lock change. · --- > Source: [citum/citum-core](https://github.com/citum/citum-core) — distributed by [TomeVault](https://tomevault.io).
files/cmd -> .jj · docs/guides/JJAICHANGESTACK.md · docs/guides/CODINGSTANDARDS.md · docs/guides/AGENTSKILLS.md · jcodemunch · &str · String · .rs
body sha256 -> 93f7f17277fd
Decide Fit First
Design Intent
How To Use It
Boundaries And Review