MyBatis-Plus Development Assistant

Problem

MyBatis-Plus usage in Java/Spring Boot often fails around dependencies, configuration, and semantic boundaries: the starter artifact changes with Spring Boot versions, pagination requires mybatis-plus-jsqlparser, Wrapper is not suitable for joins, window functions, or complex aggregation, updateById skips null fields by default, and logic delete, enum mapping, transaction rollback, and SQL injection checks can produce silent mistakes.

How It Works

The skill starts with dependency detection, checking pom.xml or build.gradle for mybatis-plus before deciding whether to activate, partially apply, or stop. It then routes to local references/ files for configuration, entity mapping, CRUD, pagination, plugins, XML, and transactions. Code guidance follows strict rules: inherit from BaseMapper / IService for single-table operations, prefer LambdaQueryWrapper with method references, move joins, GROUP BY, and window functions into XML, add the pagination interceptor last with an explicit DbType, and validate external input used in apply with {0} placeholders and injection checks.

Boundaries

It targets MyBatis-Plus 3.5.x with partial 3.4.x compatibility. Native MyBatis projects may only use the XML and transaction sections; JPA, Hibernate, DDL design, or raw SQL tuning are out of scope. Watch for version artifacts, pagination dependencies, field strategies, enum typeHandler declarations, and transaction rollbackFor settings.