SQL Table Entity Generator

Problem to Solve

When moving from a database schema to a Java backend, developers often need to create DO, Mapper, Service, and ServiceImpl classes by hand, then add MyBatis-Plus, Lombok, and Jackson annotations. When tables contain many fields, comments, primary keys, and fixed time-column rules, manual generation can miss annotations, get naming wrong, or drop field mappings. This skill converts CREATE TABLE statements into usable Java class files, reducing boilerplate and repetitive checks, while helping teams generate base code with consistent naming.

How It Works

The skill processes SQL through a fixed pipeline:
- Parse SQL: reads CREATE TABLE statements and extracts table names, columns, comments, and constraints.
- Map types: converts INT, BIGINT, DECIMAL, VARCHAR, DATETIME, BLOB, and similar MySQL types to Java types.
- Generate entities: names entity classes with a DO suffix, such as UserDO, converts fields to camelCase, and adds @Data, @Builder, no-arg and all-arg constructor annotations.
- Generate interfaces: outputs UserMapper, UserService, and UserServiceImpl.
- Add annotations: includes @TableName, @TableId, @TableField, fill rules for create_time and update_time, and @JsonFormat for ID fields.
- Preserve naming: entity classes use the DO suffix, while Mapper and Service names remain business-oriented, making module organization easier.

Boundaries and Notes

This skill targets reverse generation from MySQL CREATE TABLE statements into MyBatis-Plus Java projects. It does not replace business SQL, complex queries, or code-style checks. Generated code should still be reviewed against project dependencies and package names; if primary-key strategy, time fields, or fill rules differ, adjust the custom template. For existing entity classes, compare fields, comments, and annotations before deciding whether to overwrite the file.