crud-rest-controller

Generate a Spring REST controller with CRUD endpoints from a Spring Data repository.

106|11|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Amplicode/spring-skills --skill crud-rest-controller
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crud-rest-controller
Source: https://github.com/Amplicode/spring-skills/tree/main/skills/crud-rest-controller
Command: npx skills add https://github.com/Amplicode/spring-skills --skill crud-rest-controller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a Spring REST controller scaffold with CRUD endpoints backed by a Spring Data repository, reducing boilerplate and accelerating feature delivery.

Core Features & Use Cases

  • Generates a @RestController with standard CRUD endpoints for a given entity and repository.
  • Optional DTO mapping support, pagination, filtering, and patch operations to cover common enterprise scenarios.
  • Real-world scenario: scaffold a CRUD API for an entity like Product with repository integration, ready for customization.

Quick Start

Provide the entity name and repository, then run the skill to generate the controller.

Frequently Asked Questions about crud-rest-controller

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Can I add pagination and filtering to a Spring Data JPA REST API?

Yes, Spring Data JPA pagination is supported natively when you generate a CRUD REST controller. The scaffolding includes pagination, filtering, and patch operations to handle common enterprise API workflows efficiently.

What do I need to scaffold a CRUD API for a Spring Boot entity?

Yes, the generated Spring REST controller supports optional DTO mapping. This separates your domain entities from the API layer, allowing the scaffold to map data between your Spring Data JPA repository and the exposed REST endpoints.

How do I reduce boilerplate when creating Spring Data JPA CRUD controllers?

To scaffold a CRUD API for a Spring Boot entity, you need an existing entity class and an available Spring Data repository. The generation relies on this project context to ensure the resulting controller is compilable and follows naming conventions.

How do I reduce boilerplate when creating Spring Data JPA CRUD controllers?

Reduce Spring Data JPA CRUD controller boilerplate by auto-generating the @RestController scaffold with standard endpoints. This accelerates feature delivery by providing a clean, compilable foundation covering CRUD operations, ready for immediate customization.