reversa-standardize

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

1.5k|405|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-standardize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-standardize
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-standardize
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-standardize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy codebases accumulate inconsistent naming, formatting, and file organization over time, making them harder to read and riskier for AI agents to modify. This Skill detects the dominant style already practiced in a project and applies it consistently, without ever altering behavior.

Core Features & Use Cases

  • Pattern Detection: Analyzes the existing code to discover the dominant conventions (naming, indentation, import order, comment style) instead of imposing a foreign style; if no clear pattern exists, it asks the user to declare the target standard.
  • Gated Batch Application: Groups inconsistencies into cohesive batches and shows a diff for each one, applying changes only after explicit user approval.
  • Safe Renaming: Treats renames as reference-sensitive operations, scanning all usages or using language tooling for safe renames, and runs the test suite afterward as proof that semantics are unchanged.
  • Use Case: After running the reversa-refactor workflow on a legacy module, use this Skill to normalize variable naming and import ordering across the touched files, reviewing each diff batch before it lands.

Quick Start

Ask the agent to run /reversa-standardize on a target file or folder so it detects the project's dominant style and proposes gated diff batches for approval.

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 in a legacy project without breaking behavior?

Run the standardize step after the reversa-refactor workflow. It detects the dominant conventions already in the code, groups inconsistencies into batches, and applies each batch only after you approve its diff, with tests run afterward to confirm semantics are unchanged.

How does the skill decide which coding style to apply?

It analyzes the existing code to find the dominant pattern for naming, indentation, imports, and comments rather than imposing an external style. If no clear pattern exists, it presents the detected options and asks you to declare the target standard.

Does it require the reversa-refactor workflow to run first?

Yes. It reads the control mode from the _reversa_refactor directory and aborts with a message to run /reversa-refactor first if that directory does not exist.

Can it safely rename variables and functions across a codebase?

Yes, but renames are treated as reference-sensitive changes. It scans all usages before applying, prefers language tooling for safe renames when available, and runs the test suite afterward as confirmation.

Will it ever change code behavior during standardization?

No. The skill is explicitly limited to cosmetic and structural changes. Any step that would alter behavior is rejected and routed to the appropriate refactoring specialist instead.