reversa-standardize

Applies naming, formatting, and organization conventions to code without changing semantics.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-standardize-lacsousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-standardize
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-standardize
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-standardize-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate inconsistent naming, formatting, and file organization over time, making reviews harder and maintenance riskier. This Skill standardizes code to the project's dominant (or user-declared) style while guaranteeing that no semantic behavior changes. ## Core Features & Use Cases - Dominant Pattern Detection: Analyzes the existing codebase to discover the prevailing conventions for naming, indentation, import order, and comment style instead of imposing a foreign style. - Gated Batch Application: Groups inconsistencies into cohesive batches and shows a diff for each one, requiring explicit user approval before any code is touched. - Rename Safety Net: Treats renames as reference-sensitive operations, performing full usage scans or tool-assisted safe renames, and runs the test suite afterward as proof that semantics are preserved. - Use Case: A team inherits a Python project mixing camelCase and snake_case functions. The skill detects snake_case as dominant, proposes batched rename diffs, applies them only after approval, and confirms with a green test run. ## Quick Start Run /reversa-standardize after /reversa-refactor has been set up, optionally passing an opportunity ID like OPP-003, and approve each proposed diff batch to standardize the code.

Frequently Asked Questions about reversa-standardize

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

FAQPage Schema
How do I standardize code style without changing behavior?

Detect the dominant conventions already present in the codebase, group inconsistencies into small batches, and apply each batch only after reviewing its diff. Running the existing test suite afterward confirms that no semantic behavior changed.

How to safely rename functions across a whole project?

Safe renaming requires scanning all references before applying the change, or using a language tool with built-in safe rename support. After renaming, run the test suite to verify every call site still resolves correctly.

Does this skill work without running /reversa-refactor first?

No. The skill reads control_mode from the _reversa_refactor directory created by /reversa-refactor and aborts with an instruction to run it first if that directory is missing.

Can it apply changes automatically without approval?

No. Every change that touches project code passes through a gate showing the diff, and cosmetic mass changes are never applied silently. Outside approved gates it only writes inside the _reversa_refactor folder.

What happens if the codebase has no clear dominant style?

When no dominant pattern is detectable, the skill presents the discovered style options as a menu and lets the user explicitly declare the target convention before proposing any changes.