Jcr Refactor

Refactoring Procedure

1. If .jcr.md exists, read it first to check project conventions and exclusion patterns.
2. Read the target code and understand the overall context.
3. Reference the references to identify areas for improvement.
4. Present before/after code for each refactoring.
5. Explain the reason and effect of each refactoring.

Refactoring Types

• Extract Function — Separate independent logic from long functions into their own functions
• Extract Variable/Constant — Give names to magic values or complex expressions
• Simplify Conditionals — Flatten complex conditionals using guard clauses, early returns, etc.
• Remove Duplication — Consolidate repeated code into common functions/modules
• Improve Naming — Change to clearer names
• Improve Error Handling — Replace empty catches, swallowed errors, etc. with proper handling
• Remove Dead Code — Clean up unused variables, imports, functions

Output Format

Must follow this format:

## Refactoring Summary

- Total N refactoring suggestions
- Main types: type(count), ...

## Refactoring Suggestions

### 1. [Title] — `file_path:line_range`

**Reason**: Why this refactoring is needed

**Before**:
(current code)

**After**:
(improved code)

**Effect**: Benefits gained from this refactoring

Output language follows the user's language.

Guidelines

• Only suggest refactorings that do not change behavior. Feature additions/modifications are outside this skill's scope.
• Suggest up to 5-7 items at a time. Present the highest priority items first, and if there are additional improvement opportunities, indicate "N more possible."
• For code with tests, suggest within the scope that won't break tests.
• Respect project conventions (.jcr.md).
• When suggesting refactorings, consider potential overflow issues (integer overflow, buffer overflow, array index out-of-bounds, etc.). Ensure suggested code changes do not introduce or overlook overflow risks.