bruno-collection-generator

Generates Bruno collection files from Express, Next.js, and Fastify API routes.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/zinohome/RTMessage --skill bruno-collection-generator-zinohome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bruno-collection-generator
Source: https://github.com/zinohome/RTMessage/tree/main/.github/skills/bruno-collection-generator
Command: npx skills add https://github.com/zinohome/RTMessage --skill bruno-collection-generator-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander.

What problem does it solve? Manually writing API test collections is repetitive and error-prone when your codebase already defines the routes. This Skill converts existing API route definitions into a complete Bruno collection with environments, authentication, and organized folders. ## Core Features & Use Cases - Route-to-Collection Generation: Scans Express, Next.js, or Fastify route definitions and produces one .bru file per request with correct method, URL, body, and auth blocks. - Environment Management: Creates Development, Staging, and Production environment files with baseUrl variables and secret variable declarations. - Folder Organization: Groups requests by resource with folder.bru files and sequence numbers for logical ordering. - Use Case: You have an Express API with users and auth routes. Run the generator to produce a Git-friendly Bruno collection where the login request automatically saves the token to an environment variable for subsequent authenticated requests. ## Quick Start Generate a Bruno collection from my Express routes in ./src with bearer authentication and output it to ./bruno-collection.

Frequently Asked Questions about bruno-collection-generator

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

FAQPage Schema
How do I generate a Bruno collection from Express routes?▼

Scan your Express route definitions to extract methods, paths, and parameters, then generate one .bru file per request plus a bruno.json manifest. The generator groups routes by resource into folders and creates environment files for each deployment stage.

What is the .bru file format used by Bruno?▼

The .bru format is a plain-text DSL with blocks like meta, get/post, headers, query, body:json, auth, docs, tests, and scripts. Each file represents one request, making collections version-control friendly without proprietary formats.

Does Bruno support environment variables and secrets?▼

Yes, Bruno uses environment .bru files with a vars block for values like baseUrl and a vars:secret list to mark sensitive entries like authToken. Requests reference variables with double curly brace syntax such as {{baseUrl}}.

How do I automatically save an auth token in Bruno?▼

Use a script:post-response block in your login request to extract the token from the response and call bru.setEnvVar to store it. Subsequent requests reference the token through the auth:bearer block with {{authToken}}.

Can I add tests to Bruno requests?▼

Yes, Bruno supports a tests block where you write assertions using test and expect functions, such as checking response status codes or validating that response bodies contain expected properties like pagination metadata.