Bruno Collection Generator

Purpose

Create practical Bruno collections from API information. Prefer output that a developer can commit, review in Git, run locally, and extend in Bruno.

Inputs to gather or infer

Gather these before generating files. If some are missing, proceed with sensible placeholders and list assumptions.

• Source material: backend routes, controllers, OpenAPI snippets, curl commands, API docs, or endpoint lists.
• Target format: OpenCollection YAML, .bru, or match the repository's existing Bruno format.
• Base URL strategy: usually {{baseUrl}} in an environment variable.
• Environment names: default to local, staging, and prod when useful.
• Authentication pattern: none, bearer token, API key, basic auth, OAuth, or inherit from collection/folder.
• Desired test coverage: smoke only, happy path, full regression, or CI-ready.

Format decision