Guide · Agent skill
How to use the Spring Boot TDD Workflow skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Spring Boot TDD Workflow skill (folder name springboot-tdd) is a set of written instructions that tells an AI agent how to do test-driven development in a Java Spring Boot service. It is for Java developers who want the agent to write failing tests first, then the minimal code to pass them. After this guide you will know how to install the skill, how to ask for work so the agent uses it, and what your project needs before it works.
Spring Boot TDD Workflowaffaan-m/ECC · MIT Download the skill Quick start
- 1Download the ZIP. Download the skill ZIP from this page and unzip it. The folder contains SKILL.md.
- 2Choose a location. Place the skill folder in ~/.claude/skills/ for personal use, or in .claude/skills/ inside one project.
- 3Or upload it in the apps. In the Claude apps, go to Settings, then Capabilities, then Skills, and upload the skill.
- 4Confirm your project setup. Make sure you have a Spring Boot project with JUnit 5, Mockito, MockMvc, AssertJ, and JaCoCo through Maven or Gradle. Add Testcontainers and a container runtime if you need database tests.
- 5Ask for a test-first change. Describe a feature, bug fix or refactor in your Spring Boot code and ask for failing tests first.
- 6Check coverage. Run mvn verify or ./gradlew test jacocoTestReport and review the JaCoCo report against the 80% target.
What the skill makes the agent do
The skill is a playbook for adding features, fixing bugs or refactoring Spring Boot code. It describes a four-step loop: write tests first and confirm they fail, implement the minimal code that makes them pass, refactor while the tests stay green, and then enforce coverage with JaCoCo.
The guidance targets 80% or more coverage across unit and integration tests. It also includes example patterns for each test layer: unit tests with JUnit 5 and Mockito, web-layer tests with MockMvc, integration tests with SpringBootTest, persistence tests with DataJpaTest and Testcontainers, and CI commands for Maven or Gradle.
- Unit tests with JUnit 5 and Mockito, using Arrange-Act-Assert and explicit stubbing
- Web-layer tests with MockMvc and jsonPath assertions
- Integration tests with SpringBootTest and the test profile
- Database tests with DataJpaTest, Testcontainers and DynamicPropertySource
- Coverage with the JaCoCo Maven plugin and CI commands
Install the skill (ZIP download or Claude apps upload)
Download the skill ZIP from this page and unzip it. The skill ships as a single file named SKILL.md. Place the unzipped skill folder in one of two locations: your personal skills folder at ~/.claude/skills/ so it is available in all your projects, or a project folder at .claude/skills/ inside one repository so only that project uses it.
If you use the Claude apps instead of files on disk, you can upload the skill under Settings, then Capabilities, then Skills.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project
- Claude apps: Settings, then Capabilities, then Skills
Check what your project needs first
The skill only gives guidance. It assumes a Java Spring Boot project that already builds. Your project should use JUnit 5, Mockito, MockMvc and AssertJ, which the examples use. Database tests need Testcontainers, which requires a container runtime such as Docker. Coverage needs Maven or Gradle with the JaCoCo plugin.
The skill does not install these dependencies for you. If your team already has a different testing standard, the agent may push these conventions over the existing ones, so decide whether that fits before you enable it.
- Java and a Spring Boot project
- JUnit 5, Mockito, MockMvc and AssertJ
- Testcontainers plus a container runtime such as Docker, for database tests
- Maven or Gradle with the JaCoCo plugin
Trigger the skill with natural requests
You do not need a special command. The skill is meant for work on features, bug fixes and refactors, so describe that work in your request and mention the test-first approach if you want to be sure. The agent decides when to apply the skill based on the request.
Requests that fit the skill name the Spring Boot code you want changed and the behaviour you expect. Asking for coverage checks as part of the task makes the JaCoCo step more likely to be run.
- Add a REST endpoint to create markets in my Spring Boot service, writing the tests first and checking JaCoCo coverage.
- Fix the bug where the markets list returns the wrong page. Write a failing test first, then fix it.
- Refactor the MarketService class using the TDD workflow and keep the tests green.
- Add a repository method to find markets by name and test it against Postgres with Testcontainers.
Run the CI commands and check coverage
The skill lists the commands it expects for continuous integration. With Maven, run the test goal in parallel or run the full verify phase. With Gradle, run the test task together with the JaCoCo report task. The Maven example attaches JaCoCo's prepare-agent goal and a report goal in the verify phase, so the report is produced when you run verify.
Coverage is a target stated in the skill, 80% or more. The skill does not say what happens if the target is missed, so check the JaCoCo report yourself.
- Maven: run the test goal or the verify phase
- Gradle: run the test task together with the JaCoCo report task
mvn -T 4 test
mvn verify
./gradlew test jacocoTestReportSafety notes: scripts and network
According to the listing, this skill runs no scripts and uses no network. It consists of one SKILL.md file with guidance. It does not execute anything on its own. Commands it shows, such as Maven or Gradle builds, run only if you or the agent run them in your project.
Tests that use Testcontainers start containers through your container runtime, so they depend on that runtime being available on your machine.
- No scripts included
- No network use stated in the listing
- Commands run only when you or the agent run them
What people use it for
- Adding a new REST endpoint to a Spring Boot API with unit, MockMvc and integration tests written first
- Fixing a bug by writing a failing test that reproduces it before changing the service code
- Refactoring a service class while keeping tests green at each step
- Adding a repository query and testing it against a real Postgres container with Testcontainers
Frequently asked questions
How do I install the springboot-tdd skill?
Download the skill ZIP from this page and unzip it. Put the folder in ~/.claude/skills/ for personal use or in .claude/skills/ inside a project. In the Claude apps, you can instead upload it under Settings, then Capabilities, then Skills.
What does the springboot-tdd skill require?
It needs a Java Spring Boot project and uses JUnit 5, Mockito, MockMvc and AssertJ in its examples. Database tests need Testcontainers and a container runtime such as Docker. Coverage needs Maven or Gradle with the JaCoCo plugin.
Is the Spring Boot TDD skill free?
The listing states the licence is MIT. This page does not give pricing, so check the listing for any cost details.
Does the skill run scripts or use the network?
According to the listing, it runs no scripts and uses no network. The package is a single SKILL.md file containing guidance only. Any builds or tests run only when you or the agent start them.
Can I use this skill with Gradle instead of Maven?
Yes. The skill lists Gradle's test task together with jacocoTestReport as its CI command. The JaCoCo setup example shown in the skill is for Maven.
Why did the agent change my existing test style?
The skill sets its own testing conventions, and the agent may apply them over a different standard already in your project. If your team uses other conventions, state them in your request or do not install the skill in that project.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits Java developers building Spring Boot REST APIs who want an agent to write tests first and aim for 80% coverage with JaCoCo. It is a good way to learn how JUnit 5, Mockito, MockMvc and Testcontainers fit together. Skip it for non-Java projects, or for teams whose existing testing standard should not be replaced.
Download the skill