marjin

Refactor Rust and Elisp code to reduce duplication and enforce conventions.

8|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/smile13241324/aemacs --skill marjin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marjin
Source: https://github.com/smile13241324/aemacs/tree/main/.agents/skills/marjin
Command: npx skills add https://github.com/smile13241324/aemacs --skill marjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor and clean existing code to reduce entropy and improve maintainability in Æmacs' Rust/core and Elisp integration.

Core Features & Use Cases

  • Refactor across Rust and Elisp boundaries to improve modularity and readability.
  • Remove duplication, apply consistent patterns, and enforce coding conventions.
  • Use in real-world scenarios such as updating the core with safer interfaces or smoothing cross-language glue.

Quick Start

Run a targeted refactor pass on the current module to eliminate duplication and enforce consistency.

Frequently Asked Questions about marjin

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

FAQPage Schema
How do I refactor Rust code to improve maintainability and reduce codebase entropy?

To refactor Rust code and reduce entropy, apply targeted passes that eliminate duplication, extract consistent patterns, and enforce coding conventions, yielding safer interfaces and measurable maintainability improvements.

Can I refactor code that spans across Rust core and Elisp integration boundaries?

Yes, you can refactor across Rust core and Elisp boundaries to improve modularity by handling cross-language bindings and Elisp glue, smoothing integration layers and ensuring consistent architectural patterns.

What is the best way to remove code duplication and enforce conventions in a mixed Rust and Elisp project?

The best way to remove duplication is running a targeted refactor pass on the current module, applying consistent patterns and enforcing coding conventions across both Rust and Elisp layers for cleaner code.

Does refactoring Rust core layers provide safe, testable patches for existing codebases?

Yes, refactoring Rust core layers provides safe, testable patches that update existing code with safer interfaces, ensuring reliability while delivering measurable improvements to the codebase.

When do I need to apply pattern extraction and code cleanup for cross-language bindings?

You need pattern extraction and code cleanup for cross-language bindings when updating core interfaces or smoothing glue layers, removing duplication to improve modularity and readability across language boundaries.