refactor

Refactor Agent

Guided refactoring with automatic cross-codebase updates.

⚠️ Step 0: Verify Configuration

BEFORE starting refactoring, invoke the symfony-sk:check-config skill to ensure project is configured.

Skill: symfony-sk:check-config

If config is missing, the skill will ask the user for information. If user cancels, STOP and inform that configuration is required.

---

Mission

Perform safe refactoring operations:

• Rename (class, method, property, variable)
• Extract (method, class, interface)
• Move (file, class to different namespace)

---

Operations

Rename Class

1. Find all usages (imports, type hints, instantiations)
2. Update class name in file
3. Update all usages
4. Rename file to match class name
5. Update namespace if needed

/refactor rename class OldName NewName

Rename Method

1. Find all call sites
2. Update method declaration
3. Update all call sites
4. Update PHPDoc references

/refactor rename method ClassName::oldMethod newMethod

Rename Property

1. Find all usages (direct, getter/setter)
2. Update property declaration
3. Update getter/setter names
4. Update all usages

/refactor rename property ClassName::$oldProp $newProp

Extract Method

1. Identify code block to extract
2. Determine parameters needed
3. Determine return value
4. Create new method
5. Replace original code with call

/refactor extract method ClassName startLine endLine newMethodName

Move Class

1. Update namespace
2. Move file to new location
3. Update all imports
4. Update autoload if needed

/refactor move class App\Old\ClassName App\New\ClassName

---

Process

1. Analyze

• Find all references to the target
• Identify files that will change
• Check for conflicts (name already exists)

2. Preview

Show user what will change:

Refactor: Rename FeatureService to EngagementService

Files affected (5):
  - api/src/Service/FeatureService.php → EngagementService.php
  - api/src/Controller/FeatureAction.php (2 usages)
  - api/src/Controller/FeatureListAction.php (1 usage)
  - front/src/Service/Bll/FeatureService.php (1 import)

Proceed? [yes/no]

3. Execute

Apply changes in order:

1. Update usages first
2. Update declaration last
3. Rename file if needed

4. Verify

• Run audit on changed files
• Check for broken references

---

Safety Rules

1. Always preview before executing
2. Never refactor without user confirmation
3. Check git status - warn if uncommitted changes
4. Search thoroughly - use Grep for all patterns
5. Handle strings - warn about string references (config, routes)

---

Search Patterns

Class references

- `use <FullClassName>`
- `new <ClassName>`
- `<ClassName>::`
- `: <ClassName>` (type hint)
- `@param <ClassName>`
- `@return <ClassName>`

Method references

- `->methodName(`
- `::methodName(`
- `'methodName'` (string reference)

---

Report Format

═══════════════════════════════════════════════════════
              REFACTOR COMPLETE
═══════════════════════════════════════════════════════

Operation: Rename class FeatureService → EngagementService

Changes applied:
  ✅ api/src/Service/EngagementService.php (renamed + updated)
  ✅ api/src/Controller/FeatureAction.php (2 references)
  ✅ api/src/Controller/FeatureListAction.php (1 reference)

⚠️ Manual review needed:
  - config/services.yaml line 45 (string reference)

Run `git diff` to review all changes.
═══════════════════════════════════════════════════════