generate-openapi-from-pr

To generate OpenAPI spec changes from a pull request, provide the PR URL or number to the skill. It analyzes PR diffs, identifies affected controllers and models, and outputs OpenAPI modifications following project conventions.

Yes, you can use a PR number instead of a full URL to update API documentation. The skill accepts formats like intercom/intercom#12345 and fetches the necessary metadata and diffs to generate the OpenAPI updates.

OpenAPI codegen handles large PRs by fetching affected files incrementally. This approach ensures the analysis of API surface changes, including routes and version changes, remains efficient and accurate.

The best way to automate API docs updates from Intercom PRs is using a skill that parses the PR details, analyzes diffs for affected models and controllers, and outputs OpenAPI changes into the target repository according to existing mapping rules.

Generating OpenAPI specs from PRs does not require manual diff analysis. The skill automatically fetches PR metadata, analyzes changes to the API surface, and applies existing mapping rules to output the necessary OpenAPI modifications.

You need to regenerate OpenAPI definitions after shipping code when a PR modifies API surface elements such as controllers, models, routes, or version changes. The skill identifies these affected components from the PR diff to generate updates.