rust-simplify

Simplifies Rust code for clarity while preserving behavior within the requested edit scope.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill rust-simplify-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-simplify
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-rust/skills/rust-simplify
Command: npx skills add https://github.com/bpcakes/jig-skills --skill rust-simplify-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rust codebases often accumulate verbose patterns, redundant clones, and deeply nested control flow that obscure intent. This Skill refactors Rust code into idiomatic, readable form without changing behavior, keeping edits confined to the scope the user requested. ## Core Features & Use Cases - Idiomatic Refactoring: Applies Rust conventions such as the ? operator, let else, iterator combinators, From/Into conversions, and proper ownership patterns. - Scope-Aware Editing: Restricts changes to working changes, a feature branch diff, a base ref comparison, or explicitly named files. - Behavior Preservation: Guarantees functionality, outputs, and ownership semantics remain unchanged, and runs existing compile/lint checks when available. - Use Case: After finishing a feature branch, ask for a simplification pass so nested match chains become early returns and redundant .clone() calls are removed before opening a pull request. ## Quick Start Ask the agent to simplify the Rust code in your current working changes while preserving behavior and reporting what it changed.

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 without changing its behavior?

Request a simplification pass scoped to your working changes or named files. The Skill applies idiomatic patterns like the `?` operator, `let else`, and iterator combinators while preserving all functionality, outputs, and ownership semantics.

How to refactor Rust code on a feature branch only?

Specify the feature branch scope so the Skill compares HEAD to the merge base with the default branch and refines only the relevant changed code. You can also name a base ref or specific files to narrow the edit scope further.

Does Rust simplification work with older editions or MSRV constraints?

Yes, the Skill respects the project's declared edition and minimum supported Rust version. It avoids suggesting idioms or standard library features that would violate those constraints.

Can I get a review-only report instead of code edits?

Yes, for review-only requests the Skill reports findings without editing any code. It only implements changes when they are explicitly part of the user's request.

What are the limitations of automated Rust simplification?

The Skill deliberately avoids over-simplification, such as overly dense iterator chains or excessive macros, that would hurt readability or debuggability. It also stays within the requested scope and will not expand into broader refactors on its own.