e2e-apidog-schema-gen-mm

Generate and patch Apidog response schemas from observed E2E request/response data.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kangmomin/harness-plugins --skill e2e-apidog-schema-gen-mm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-apidog-schema-gen-mm
Source: https://github.com/kangmomin/harness-plugins/tree/main/plugins/minmos-harness/skills/e2e-apidog-schema-gen-mm
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill e2e-apidog-schema-gen-mm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E tests produce real request/response data that must be reflected in Apidog specifications; this Skill automates syncing those results to keep documentation aligned with actual behavior.

Core Features & Use Cases

  • Syncs observed E2E results (requests/responses) into Apidog schema definitions.
  • Generates and patches response schemas for both successful and error responses.
  • Validates against the current OAS and reconciles gaps to maintain consistency with implementation.

Quick Start

Execute the e2e-apidog-schema-gen-mm workflow to propagate the latest E2E results into Apidog.

Frequently Asked Questions about e2e-apidog-schema-gen-mm

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

FAQPage Schema
How do I sync E2E test results into Apidog schemas automatically?

To sync E2E test results into Apidog schemas, this Skill collects observed request and response data to generate or adjust response schemas for both 2xx successes and error statuses, producing a flat-inlined output suitable for Apidog ingestion.

Can I generate both success and error response schemas from E2E testing data?

You can generate both success and error response schemas from E2E testing data by applying observed request and response results to create or adjust specifications across relevant endpoints for 2xx successes and error statuses.

How does syncing E2E results maintain consistency with existing OpenAPI specifications?

Syncing E2E results maintains consistency with existing OpenAPI specifications by validating collected data against the current OAS, reconciling discrepancies, and producing a deterministic schema output that aligns documentation with actual behavior.

What is the best way to update Apidog specifications from real request and response data?

The best way to update Apidog specifications from real request and response data is to automate syncing E2E results, which reconciles gaps between implementation and existing OAS to keep documentation aligned with actual behavior.

Do I need existing OpenAPI specifications to reconcile E2E testing discrepancies in Apidog?

You need existing OpenAPI specifications to validate observed E2E request and response data, reconcile any discrepancies, and ensure the generated flat-inlined schema output remains consistent before Apidog ingestion.