mapper-to-api-spec

Analyze SQL Server Mapper files to generate OpenAPI 3.0 RESTful API specifications.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/goodispeter/my-agent-skill --skill mapper-to-api-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mapper-to-api-spec
Source: https://github.com/goodispeter/my-agent-skill/tree/main/mapper-to-api-spec
Command: npx skills add https://github.com/goodispeter/my-agent-skill --skill mapper-to-api-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of analyzing SQL Server Mapper files (like MyBatis or JPA) and automatically generating comprehensive RESTful API specifications. It bridges the gap between direct database access and modern API-driven architectures.

Core Features & Use Cases

  • Automated API Specification Generation: Analyzes SQL Server Mapper configurations (MyBatis XML/Java, JPA) to derive API endpoints, request/response structures, and OpenAPI 3.0 specifications.
  • Mapper to API Mapping: Creates detailed documentation mapping original Mapper methods to their corresponding API endpoints, including how parameters are translated and how merged methods can be restored.
  • RESTful Design Adherence: Designs APIs following RESTful best practices, including correct HTTP method usage, resource naming, and parameter standardization.
  • Use Case: Imagine a legacy system with extensive direct database access via MyBatis Mappers. This Skill can analyze those Mappers and generate a complete OpenAPI specification for a new RESTful API layer, significantly accelerating the migration to an API-first architecture.

Quick Start

Use the mapper-to-api-spec skill to analyze the SQL Server Mapper files located at D:\workspace\oms\OMS_StudyProgress\dal_products and generate the corresponding API specification documents.

Frequently Asked Questions about mapper-to-api-spec

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

FAQPage Schema
How do I generate OpenAPI specifications from MyBatis Mapper files?

Generating OpenAPI specifications from MyBatis Mapper files involves analyzing SQL Server Mapper configurations to derive RESTful API endpoints, request/response structures, and OpenAPI 3.0 documents automatically. This process bridges direct database access and API-driven architectures by consolidating Mapper methods into standardized API designs.

How do I convert direct database access to RESTful APIs for legacy migration?

Converting direct database access to RESTful APIs requires analyzing existing SQL Server Mapper files to map original methods to new API endpoints. This includes designing correct HTTP methods, standardizing parameters, and generating DTOs to facilitate migration from legacy database access layers to an API-first architecture.

What is the process for deriving API endpoints from JPA repositories?

Deriving API endpoints from JPA repositories involves analyzing the repository methods to discover database access patterns, consolidating similar methods, and designing RESTful resource naming conventions. The process automatically generates the corresponding API endpoints and OpenAPI 3.0 specification documents for the new API layer.

Can I analyze both MyBatis XML and JPA configurations to generate RESTful API specifications?

Yes, analyzing both MyBatis XML/Java and JPA configurations supports automated RESTful API specification generation. The process reads SQL Server Mapper files, derives the API endpoints and DTOs, and assembles a comprehensive OpenAPI 3.0 document mapping the original database access methods to the new API architecture.

How are Mapper method parameters translated into RESTful API endpoints?

Mapper method parameters are translated into RESTful API endpoints through deep analysis and method consolidation. The process maps original database access parameters to standardized request and response structures, documenting how parameters are translated and how merged methods can be restored in the final OpenAPI specification.