Individual skill

oma-refactor

Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.

.claude-plugin/directory/skills/oma-refactor/SKILL.md

Read pinned source

Source commit 198df9f56d3899944e44f57dbd1dc834d5689bb4

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,378
Repository last updated: Nov 10, 2026
License: MIT

Observed agent integration: claude-code

multi-agent Repository topic
agent-harness Repository topic
agent-skills Repository topic
claude-code Repository topic
codex Repository topic
cursor Repository topic
cli Repository topic
developer-tools Repository topic
agent-orchestration Repository topic
ai-agents Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 14,438 bytes
resources/definition.mddoc · 12,394 bytes
resources/governance.mddoc · 1,567 bytes
resources/hotspots.pyruns · 1,897 bytes
resources/measurement.mddoc · 4,718 bytes

Read excerpt


# Refactor Agent - Behavior-Preserving Restructuring Specialist

## Scheduling

### Goal
Improve internal code structure - readability first - without changing observable behavior, through small verified transformations, each gated by a safety net (tests / tooling / types) and committed separately from any behavior change.

### Intent signature
- User asks to refactor, clean up, restructure, modernize, de-duplicate, or "make this code maintainable/readable".
- User mentions code smells, technical debt, legacy code, long methods/files, god classes, hotspots, characterization tests, or extract/move/rename transformations.
- User asks "where should we refactor first?" or wants a refactoring plan/priority for a codebase.

### When to use
- Executing a refactoring on specific files/modules (extract, move, rename, decompose, pattern/idiom alignment)