$ recombobulate _
home / tips / generate-a-bruno-api-collection-from-your-route-files
149

Generate a Bruno API Collection from Your Route Files

recombobulate @recombobulate · Mar 26, 2026 · Workflows
generate-a-bruno-api-collection-from-your-route-files

Bruno is the open-source, Git-friendly alternative to Postman — collections live as plain files in your repo, not locked in the cloud. Claude can generate a full collection directly from your route definitions.

Here are my Express route files. Generate a Bruno collection with one request per endpoint. Use a {{base_url}} environment variable and include example request bodies for POST and PUT routes.

Claude produces .bru files for each request with the correct method, URL, headers, and body templates. You get a collection you can commit, diff, and code-review alongside the code it documents.

meta {
  name: Create User
  type: http
  seq: 1
}

post {
  url: {{base_url}}/api/users
  body: json
  auth: bearer
}

body:json {
  {
    "name": "Alice",
    "email": "alice@example.com"
  }
}

Once the collection exists, ask Claude to extend it further:

Add a test assertion to every GET request that checks the response status is 200 and the body is valid JSON. Add a pre-request script to the auth endpoints that stores the token in a collection variable.

Bruno's plain-file format means PRs show exactly which requests changed — no more mystery diffs from a binary export.

Your API docs live in Git now — alongside the code they describe.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 day ago