freemcplab / Directory / Playground / sivalabs-agent-skills

● Community sivaprasadreddy ⚡ Instant

sivalabs-agent-skills

Name: sivalabs-agent-skills (Claude Skill)
Author: sivaprasadreddy

by sivaprasadreddy · sivaprasadreddy/sivalabs-agent-skills

Spring Boot skills for AI coding agents — idiomatic Boot 3.x, Testcontainers, Jakarta EE patterns.

sivalabs-agent-skills encodes Spring Boot best practices from Siva Katamreddy: modern Boot 3.x features, constructor injection, Jakarta namespace, Testcontainers for integration tests, Flyway, validation, OpenAPI, and common pitfalls. Clone once and Claude writes Boot code that actually looks like what Boot developers write in 2025, not 2017.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Targets Spring Boot 3.x and Java 17/21
Idiomatic constructor injection — no field-level @Autowired
Testcontainers-first integration test patterns
Flyway migrations and layered project structure
OpenAPI, bean validation, and error-handling conventions

Live Demo

What it looks like in practice

sivalabs-agent-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use sivalabs-agent-skills

How to scaffold a Spring Boot service with modern defaults

👤 Java developers starting a new Boot service ⏱ ~60 min intermediate

When to use: Greenfield Boot project and you don't want to re-decide every convention.

Flow

Describe the service

Scaffold a Spring Boot 3.2 REST service 'orders-service' with JPA, PostgreSQL, Flyway, and Testcontainers.✓ Copied

→ Proper project layout + pom/build.gradle + baseline migrations
Add a feature

Add an /orders endpoint with POST/GET and validation.✓ Copied

→ Controller + service + repository + validation
Integration tests

Add integration tests using Testcontainers PostgreSQL.✓ Copied

→ Tests boot a container, hit endpoints, pass

Outcome: A running Boot service with tests.

Pitfalls

Claude defaults to field injection — Skill prompts constructor injection; if not, re-ask explicitly

Combine with: filesystem · github

Migrate a Boot 2.x service to 3.x (Jakarta namespace)

👤 Teams carrying Boot 2.x tech debt ⏱ ~180 min advanced

When to use: You've been putting off the javax → jakarta migration.

Flow

Audit

Audit this project — list everything that needs to change for Boot 3.✓ Copied

→ Full change list: imports, plugin versions, config properties
Execute the shift

Apply the jakarta namespace shift and upgrade dependencies.✓ Copied

→ Passing compile after edits
Fix the broken tests

Fix tests that broke — usually Mockito strictness or auto-config changes.✓ Copied

→ Green tests

Outcome: A migrated service you can actually merge.

Pitfalls

Missed javax references in config or third-party libs — Use the migrator's report + a grep sweep

Combinations

Pair with other MCPs for X10 leverage

sivalabs-agent-skill + filesystem

Operate across a multi-module Boot project

Walk my Boot project and add Testcontainers to every persistence module.✓ Copied

sivalabs-agent-skill + github

Open PRs with concise migration steps

Open a PR titled 'chore: migrate orders-service to Boot 3.2'.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
boot-scaffolding	service intent + stack	Greenfield
testcontainers-integration	service + container stack	Whenever persistence is involved
boot-2-to-3-migration	project root	Upgrade tasks

Cost & Limits

What this costs to run

API quota: none
Tokens per call: 5–25k per task
Monetary: free
Tip: Migrate one module at a time; don't dump the monorepo on Claude

Security

Permissions, secrets, blast radius

Credential storage: none at skill level

Data egress: none

Troubleshooting

Common errors and fixes

Testcontainers fails in CI

Ensure CI has Docker available and the runner supports privileged containers.

Verify: docker ps

Flyway migration fails on existing DB

Ask Claude for a baseline migration and mark existing schema.

Alternatives