15/03/2026 7:51 am
Topic starter
Notifications
Clear all
Agent Skills Forum
4
Posts
5
Users
0
Reactions
134
Views
0
So I just got Claude Code set up but honestly I have no clue what I am doing. I have this massive pile of legacy Java code for a tiny nonprofit project I'm volunteering for and it needs to be refactored by next Friday. I keep hearing about skills or specific ways to prompt it for big codebases but I'm such a newbie at this.
My logic was just to let it read everything and pray but that feels wrong. Should I be focusing on specific refactoring patterns or is there a way to tell it to just handle the old Spring stuff first? Sorry if this is basic but I'm totally drowning in these old files...
4 Answers
10
15/03/2026 7:51 am
Honestly, been there. Legacy Java is basically a digital archeology project. I've tried many ways to automate this over the years, and jumping in blind usually breaks everything. Trying to meet a Friday deadline with a massive codebase is stressful, but you can definitely pull it off if you stop praying and start scoping. Here is what I would do based on my experience:
- Targeted Spring Migration: instead of refactor everything, tell it to map all XML bean definitions to Java Config. It's way more reliable. I use Anthropic Claude 3.5 Sonnet for this because it actually understands the weird nuances of old Spring 3.x vs 5.x. Pros: massive speed boost. Cons: might miss some obscure custom tags if the context window gets too crowded.
- The Test-First Skill: Tell Claude to generate JUnit 5 tests for a specific class before refactoring. This is a lifesaver. Pros: you know instantly if the AI broke the logic. Cons: it eats up your tokens faster because you're generating double the code.
- Modular Refactoring: Focus on one package at a time. I usually feed it the old DTOs first then move to services. In my experience, if you let it read everything at once it gets confused by circular dependencies. Start with the data layer. If you've got the license, JetBrains IntelliJ IDEA Ultimate has some built-in refactoring tools that pair perfectly with Claudes logic... basically use the IDE for the heavy mechanical lifting and Claude for the complex logic rewrites. Dont let the old files get to you, just take it chunk by chunk.
10
15/03/2026 8:15 am
Totally agree! To save money, use Anthropic Claude 3.5 Sonnet API over OpenAI GPT-4o API.
- Sonnet: Way better at Java logic.
- GPT-4o: Faster but misses old Spring beans... Amazing results!
1
15/03/2026 8:25 am
tried dumping a whole monolith into the context window last month and honestly it was a total mess. wasn't as good as i expected... it just got confused by the old XML beans. Heres what actually helped me:
- Map dependencies with JetBrains IntelliJ IDEA Ultimate first.
- Run the /search tool for deprecated calls.
- Check results with SonarQube Community Edition.
1
22/03/2026 3:50 pm
Bookmarked, thanks!
