skills.rest
imMamdouhaboammar
imMamdouhaboammarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agency-rust-refactoring-specialist

Coordinate repository-scale Rust refactoring across modules, traits, and types.

Updated Jul 24, 2026
Search Tags:#refactoring#ownership#rust#code-quality#clippy#systems-engineering
One-click install
npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-rust-refactoring-specialist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-rust-refactoring-specialist
Source: https://github.com/imMamdouhaboammar/kaku-chatgpt-harness/tree/main/.agents/skills/engineering-rust-refactoring-specialist
Command: npx skills add https://github.com/imMamdouhaboammar/kaku-chatgpt-harness --skill agency-rust-refactoring-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of large-scale Rust codebase maintenance, ensuring that refactoring tasks like module restructuring, ownership improvements, and compiler remediation are performed safely without introducing regressions or breaking public APIs.

Core Features & Use Cases

  • Repository-Scale Refactoring: Executes coherent change sets across crates, modules, and tests, ensuring no half-migrations or stale references remain.
  • Evidence-Based Auditing: Provides detailed inventories of refactoring opportunities, including ownership improvements and panic hardening, backed by technical evidence.
  • Contract Preservation: Ensures that public API shapes, serialization formats, and side effects remain intact unless explicit authorization for breaking changes is provided.

Quick Start

Use the agency-rust-refactoring-specialist skill to audit the current crate for ownership improvements and propose a refactoring plan.

Frequently Asked Questions about agency-rust-refactoring-specialist

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

FAQPage Schema
How do I safely restructure Rust modules and traits across a large crate without breaking the public API?▼

Repository-scale Rust refactoring coordinates structural changes across modules, traits, and types while preserving public API contracts and serialization formats. It analyzes call graphs and feature-gated code to ensure coherent code evolution without regressions.

What's the best way to optimize Rust ownership and borrowing across multiple modules?▼

Ownership optimization in Rust requires comprehensive call graph analysis to identify borrowing improvements across modules and traits. Evidence-based auditing provides detailed inventories of refactoring opportunities backed by technical evidence, ensuring semantic correctness during structural changes.

How do I harden Rust code against panics during a large refactoring project?▼

Panic hardening during Rust refactoring involves analyzing feature-gated code and call graphs to identify panic points across modules. Structural changes are coordinated while maintaining semantic correctness, ensuring panic remediation doesn't introduce regressions or break public API contracts.

Can I fix all Clippy warnings across a repository without leaving stale references?▼

Clippy remediation at repository scale executes coherent change sets across crates, modules, and tests, ensuring no half-migrations or stale references remain. The process requires analyzing call graphs and public API contracts to maintain semantic correctness during compiler remediation.

Does Rust refactoring work safely with feature-gated code and complex type hierarchies?▼

Rust refactoring handles feature-gated code by analyzing call graphs and type hierarchies comprehensively before applying structural changes. Contract preservation ensures public API shapes and side effects remain intact unless explicit authorization for breaking changes is provided.

When should I avoid automated Rust refactoring for ownership improvements?▼

Avoid Rust refactoring without explicit authorization for breaking changes if public API contracts, serialization formats, or side effects must remain intact. Safe refactoring requires comprehensive analysis of call graphs and feature-gated code to prevent regressions during structural evolution.

Related Skills

Explore More Software Engineering Skills→
wcyganwcygan
1

rust-crate-creator

Create a new Rust crate with workspace dependency pinning and standard documentation.

Community
Intermediate
termidetermide
138

refactor

Analyze Rust codebases and apply scoped refactors validated by cargo clippy and cargo test.

Official
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

clippy-lints

Apply Clippy linting to Rust codebases with custom configuration.

Official
Advanced
xenitV1xenitV1
230

tdd-mastery

Enforce test-first discipline with failing tests before production code.

Community
Basic