Use this skill strictly for behavior-preserving code improvements. If you need to fix a bug or add functionality, use the bug-fixing or standard coding flow instead.

Core Principles

Zero Behavior Change: The code MUST produce the same output for the same input after refactoring.
Small, Reversible Steps: Make incremental changes that can be easily reverted if a test fails.
Clean Code Focus: Focus on readability, maintainability (DRY, SOLID), and removing technical debt.

Refactoring Process

Baseline: Ensure existing tests pass. If no tests exist, write them before refactoring.
Identify Smells: Long methods, dead code, logic duplication, or poor naming.
Apply Pattern: Use established patterns like "Extract Method", "Rename Variable", or "Simplified Conditionals".
Verify: Run tests after every small change to confirm no breakage.

[!TIP] Refactoring is a "clean as you go" process. It should make future changes easier, not change what the code does today.

Más de este repositorio

mismo repositorio

coding-in-ruby-on-rails

kishan04rajput/ai-ide-rules

Follow these rules while coding in ruby on rails.

2026-05-130

coding-in-react-native-expo

kishan04rajput/ai-ide-rules

Best practices and rules for coding in React Native Expo projects, specifically using Expo Router.

2026-04-290

create-skill

kishan04rajput/ai-ide-rules

Guides users through creating effective Agent Skills. Use when the user wants to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.

2026-01-240

bug-fixing

kishan04rajput/ai-ide-rules

Systematic process for implementing minimal, intelligent bug fixes in any language (Implementation Only).

2026-01-220

identify-bugs

kishan04rajput/ai-ide-rules

Systematic process for identifying and analyzing bugs (Identification Only).

2026-01-220

variable-name-update

kishan04rajput/ai-ide-rules

Guidelines and systematic process for updating variable, function, and class names to improve code readability and maintainability.

2026-01-200

name	refactoring
description	Improving internal code structure without changing external behavior.

Refactoring Skill

Use this skill strictly for behavior-preserving code improvements. If you need to fix a bug or add functionality, use the bug-fixing or standard coding flow instead.

Core Principles

Zero Behavior Change: The code MUST produce the same output for the same input after refactoring.
Small, Reversible Steps: Make incremental changes that can be easily reverted if a test fails.
Clean Code Focus: Focus on readability, maintainability (DRY, SOLID), and removing technical debt.

Refactoring Process

Baseline: Ensure existing tests pass. If no tests exist, write them before refactoring.
Identify Smells: Long methods, dead code, logic duplication, or poor naming.
Apply Pattern: Use established patterns like "Extract Method", "Rename Variable", or "Simplified Conditionals".
Verify: Run tests after every small change to confirm no breakage.

[!TIP] Refactoring is a "clean as you go" process. It should make future changes easier, not change what the code does today.