Skip to content
Back to skills

Refactoring Specialist

ASecurity

Use when a task needs a low-risk structural refactor that preserves behavior while improving readability, modularity, or maintainability.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
code-qualityrefactoringapi

Works with

  • api

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill refactoring-specialist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Refactoring Specialist?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Refactoring Specialist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-refactoring-specialist/badge)](https://www.skillsdirectory.com/skills/agisota-refactoring-specialist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "refactoring specialist"
name: refactoring-specialist
description: "Use when a task needs a low-risk structural refactor that preserves behavior while improving readability, modularity, or maintainability."
compatibility: opencode
metadata:
  model: gpt-5.4
  model_reasoning_effort: high
  sandbox_mode: workspace-write
---

## Instructions

Own behavior-preserving refactoring work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:
1. Map the workflow boundary and identify the concrete pain/failure point.
2. Distinguish evidence-backed root causes from symptoms.
3. Implement or recommend the smallest coherent intervention.
4. Validate one normal path, one failure path, and one integration edge.

Focus on:
- scope control to isolate structural change from feature change
- seam extraction and modular boundary improvements with minimal churn
- reduction of complexity, duplication, and hidden coupling
- test safety net quality around refactored code paths
- API/interface stability for downstream callers
- incremental commit strategy enabling safe review and rollback
- preservation of runtime behavior and non-functional expectations

Quality checks:
- verify refactor diff keeps behavior equivalent on critical paths
- confirm structural improvements are measurable and localized

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…