skills.rest
shiaho777
shiaho777COMMUNITY
Explore all skills by this author →
Website𝕏@shiaho777GitHub

refactor

Refactor code to restructure projects without changing runtime behavior.

5.5k|794|Updated Nov 26, 2025
Search Tags:#quality#refactor#plan#software-engineering#code-cleanup#edits#read-before-edit
One-click install
npx skills add https://github.com/shiaho777/web-to-app --skill refactor-shiaho777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/shiaho777/web-to-app/tree/main/app/src/main/assets/skills/refactor
Command: npx skills add https://github.com/shiaho777/web-to-app --skill refactor-shiaho777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restructure and clean up existing code without changing runtime behavior, reducing technical debt and improving readability.

Core Features & Use Cases

  • Read-before-edit discipline to ensure changes are informed
  • One-change-per-turn rule to limit scope and risk
  • Plan edits before applying them and verify references afterward
  • Avoid introducing new abstractions unless explicitly requested

Quick Start

Initiate a focused refactor on the target files to achieve the stated goal while preserving behavior.

Frequently Asked Questions about refactor

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

FAQPage Schema
How do I refactor code without changing runtime behavior?▼

Safe code refactoring requires reading the target files first, planning the edits, applying one change per turn, and verifying references afterward to preserve runtime behavior across single-file or multi-file modules.

What is the one-change-per-turn rule for code cleanup?▼

The one-change-per-turn rule limits each code cleanup cycle to a single modification, reducing risk and preventing unintended side effects during architectural improvements or multi-file module restructuring.

Can I introduce new abstractions when restructuring existing code?▼

No, you should avoid introducing new abstractions during a refactor unless explicitly requested. The goal is to restructure existing code, reduce technical debt, and improve readability without expanding the architectural footprint.

Does this refactoring approach work for multi-file modules?▼

Yes, this refactoring approach works for both single-file edits and multi-file modules. It enforces read-before-edit discipline and post-edit reference verification to safely apply architectural improvements across project maintenance and feature cleanups.

Why do I need to read code before editing during a refactor?▼

Reading code before editing ensures changes are informed by existing structure and logic. This read-before-edit discipline prevents accidental runtime behavior changes and helps verify that all references remain intact after modifications.

Related Skills

Explore More Software Engineering Skills→
coco-researchcoco-research
264

pmstudio-sync

Synchronize linked project documents by proposing precise edits for approval.

Community
Advanced
reckerswartzreckerswartz

tdd-refactoring-agent

Refactor Rails apps with deterministic steps while keeping tests green.

Community
Advanced
sumilee-pcusumilee-pcu

tech-debt

Scan source code for TODOs and complexity hotspots to manage technical debt.

Community
Intermediate
kk20300113-pngkk20300113-png

plankton-code-quality

Format and lint code on every file edit in Claude Code workflows.

Community
Advanced