skills.rest
christianhelle
christianhelleCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

multi-source-openapi-tooling

Diagnose Refitter multi-source OpenAPI loading and merging failures from .refitter files.

413|64|Updated Feb 7, 2023
Search Tags:#debugging#openapi#diagnostics#tools#multi-document#path-resolution#refitter
One-click install
npx skills add https://github.com/christianhelle/refitter --skill multi-source-openapi-tooling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-source-openapi-tooling
Source: https://github.com/christianhelle/refitter/tree/main/.squad/skills/multi-source-openapi-tooling
Command: npx skills add https://github.com/christianhelle/refitter --skill multi-source-openapi-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses how Refitter handles multi-source OpenAPI specifications loaded from .refitter files.

Core Features & Use Cases

  • Detects when openApiPaths production flow fails due to per-spec or merged document inconsistencies.
  • Provides isolation steps by generating per-spec OpenAPI specs to verify load and resolution paths.
  • Guides debugging across CLI, source-generator, and MSBuild tooling when multi-document merges produce conflicting schemas.

Quick Start

Run a per-spec sanity check on a .refitter file containing openApiPaths to verify load, path resolution, and merge behavior.

Frequently Asked Questions about multi-source-openapi-tooling

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

FAQPage Schema
How do I debug multi-source OpenAPI merge failures in Refitter?▼

To debug multi-source OpenAPI merge failures in Refitter, run a per-spec sanity check on your .refitter file to validate individual load paths and settings before attempting a full multi-document merge.

Why does Refitter fail path resolution for openApiPaths in my .refitter file?▼

Refitter path resolution for openApiPaths fails when individual OpenAPI specifications contain inconsistencies or invalid paths. Isolating each spec generation helps pinpoint exactly which document's load or resolution path is breaking.

Can I diagnose Refitter multi-document issues across CLI, MSBuild, and source-generator workflows?▼

Yes, you can diagnose Refitter multi-document issues across CLI, MSBuild, and source-generator workflows by generating isolated OpenAPI specs to verify load behavior and clear GeneratedFile markers to locate merge conflicts.

What is the best way to validate multiple OpenAPI paths before merging in Refitter?▼

The best way to validate multiple OpenAPI paths before merging in Refitter is to perform per-spec validation, generating each spec in isolation to verify that all schemas resolve correctly without conflicting.

How do I pinpoint where conflicting schemas break a multi-document OpenAPI merge?▼

To pinpoint where conflicting schemas break a multi-document OpenAPI merge, use clear GeneratedFile markers and isolated-spec generation to identify the exact source document causing the loading or merging failure.

Related Skills

Explore More Software Engineering Skills→
christianhellechristianhelle
413

tunit-test-filtering

Run focused TUnit tests via treenode filters on the compiled test executable.

Community
Intermediate
JaimeJunrJaimeJunr
2

fix-merge-conflicts

Resolve merge conflicts and verify builds and tests.

Community
Advanced
pluginagentmarketplacepluginagentmarketplace
1

documentation

Generate API documentation from OpenAPI 3.1 specifications.

Community
Intermediate
assertchrisassertchris
2

custom-conflict-resolution

Resolve Git merge conflicts file by file using a rebase strategy.

Community
Advanced