rust-simplify

Simplify one Rust file by reducing duplication and nested control flow.

31|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/citum/citum-core --skill rust-simplify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-simplify
Source: https://github.com/citum/citum-core/tree/main/.skills/rust-simplify
Command: npx skills add https://github.com/citum/citum-core --skill rust-simplify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes avoidable Rust complexity and code smells in the Citum workspace, improving readability and maintainability without changing behavior unexpectedly.

Core Features & Use Cases

  • One-file Rust quality pass: Simplifies nested control flow, reduces duplication, and targets high-value cleanup using symbol and file analysis.
  • Ownership and performance-aware edits: Encourages idiomatic Rust patterns, explicit error handling, and borrowed lookups with controlled allocation boundaries.
  • Guardrailed verification workflow: Runs the repo-required Rust checks and the Rust smell audit script, then documents the exact commands and results.

Quick Start

Run rust-simplify to select the highest-value Rust file to clean up, perform the simplification, and verify the changes with the required Rust checks and the Rust review-smells audit.

Frequently Asked Questions about rust-simplify

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

FAQPage Schema
How do I simplify Rust code with nested control flow and duplication in one pass?

Rust code simplification targets high-value files using symbol and file analysis, reducing nested control flow and duplication in a bounded one-file pass that improves idiomatic structure without unexpected behavior changes.

What is the best way to reduce Rust code smells across a workspace?

Reducing Rust code smells involves a focused one-file quality pass that fixes avoidable complexity, improves ownership and borrowing patterns, and runs a smell audit script to verify improvements across the workspace.

Does Rust refactoring require running specific verification checks after cleanup?

Rust refactoring verification requires running repo-required Rust checks and a smell audit script after cleanup, documenting exact commands and results to ensure correctness and standards compliance.

Can I use a one-file Rust cleanup pass for maintenance tasks instead of bug fixes?

A one-file Rust cleanup pass targets maintenance tasks where code cleanup is needed rather than specific bug fixes, selecting the best file via symbol analysis and limiting scope to idiomatic structure and duplication reduction.

What limitations apply when simplifying Rust code with ownership and borrowing improvements?

Simplifying Rust code with ownership improvements requires adherence to repo Rust coding standards and controlled allocation boundaries, bounded to one file per pass to avoid unexpected behavior changes during refactoring.