Explain legacy claims code
UnderstandWorking in the older Java claims system.
Explain what [class name] does in plain English. Map out the methods that change claim state, and flag anything that depends on global state or old framework behavior.
Hi! Ask me anything about Copilot.
Answers are written for your team and link to the official GitHub docs they come from.
Written by Claude, an AI model. Double-check anything important in the linked docs.
Copy-ready prompts for Copilot Chat, written for Bluestone Assurance. Fill in the parts in [brackets] and paste.
Working in the older Java claims system.
Explain what [class name] does in plain English. Map out the methods that change claim state, and flag anything that depends on global state or old framework behavior.
Setting up custom instructions for a repo.
Draft a .github/copilot-instructions.md for [repo] describing our Java version, frameworks, naming rules, and how we write tests, in under 15 lines.
Building a new policy admin feature.
Using the patterns in [folder], implement [feature] with validation, an audit log entry, and unit tests. Match our existing naming and error handling.
Before you change code with no tests.
Write characterization tests for [class] that capture its current behavior, including odd edge cases, so I can refactor it safely.
Making a small, tested change to old code.
Refactor [method] to modern Java without changing behavior. Replace raw types and long if-else chains, keep the public signature, and list tests I should run first.
A pull request touches claims logic.
Review this diff for behavior changes in claim calculations, missing null checks, and gaps in tests. Point to exact lines and suggest fixes.
Bluestone AssurancexCopilot
Customer success portal
Elena Ruiz
Senior Director of Engineering