Covers Spring Code Analysis Testing Debugging
Description
MUST be used whenever a user or agent asks to find problems, check for issues, or validate changes in a Spring Boot project. Uses the spring-tools MCP server to check for validation problems in the project's source files.
SKILL.md
CRITICAL REQUIREMENT: Whenever a user asks for problems or validations or diagnsotics or problem markers in the project, or an agent is attempting to check if there are problems with the project, or attempts to validate changes to the project, IF the project is a Spring Boot project, then the spring-tools plugin MCP server MUST be used to check for validation problems in each source file of the project.
To perform this validation:
- Use the
getDiagnosticstool from the spring tools MCP server to get a list of diagnostics for a specific project. You need to pass in the name of the project. If you are not sure about the exact name, you can invokegetProjectListfrom the spring tools MCP server to get the exact names of the projects in the current workspace. - Carefully review the returned diagnostics.
- Identify the specific error code, file path, and text range for each Spring-related diagnostic (e.g. error code "WEB_SECURITY_CONFIGURER_ADAPTER").
- For every Spring-specific error code you encounter, you MUST invoke the
/spring-tools:quickfixskill, passing the error code, the file path, and the text range as arguments, to retrieve the official explanation and fix instructions. - Apply the appropriate fix based on the instructions, or ask the user if a choice needs to be made.
- Also ensure any standard Java compilation or build errors are addressed.