rust-simplify
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: rust-simplify
description: One-file-at-a-time Rust quality pass for Citum, using jcodemunch to target the highest-value cle…
category: other
runtime: no special runtime
---
# rust-simplify output preview
## PART A: Task fit
- Use case: One-file-at-a-time Rust quality pass for Citum, using jcodemunch to target the highest-value cleanup. Use when this capability is needed. Use this skill for bounded Rust cleanup work in the Citum workspace when the task is to runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Target Selection / Quality Pass / Verification” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “One-file-at-a-time Rust quality pass for Citum, using jcodemunch to target the highest-value cleanup. Use when this capability is needed. Use this skill for bounded Rust cleanup work in the Citum workspace when the task is to runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Target Selection / Quality Pass / Verification” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Target Selection / Quality Pass / Verification”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: rust-simplify
description: One-file-at-a-time Rust quality pass for Citum, using jcodemunch to target the highest-value cle…
category: other
source: tomevault-io/skills-registry
---
# rust-simplify
## When to use
- One-file-at-a-time Rust quality pass for Citum, using jcodemunch to target the highest-value cleanup. Use when this ca…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Target Selection / Quality Pass / Verification” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "rust-simplify" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Target Selection / Quality Pass / Verification
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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.
Source: citum/citum-core — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review