Generate a Postman Collection from Your Route Files
Keeping a Postman or Insomnia collection in sync with your actual routes is a chore that almost nobody does consistently. Claude can generate an importable collection directly from your route definitions.
Read routes/api.php and generate a Postman collection v2.1 JSON
file. Group endpoints by resource, include example request bodies
for POST/PUT routes based on the validation rules in the
corresponding FormRequest classes, and add a Bearer token
auth variable.
Claude reads your route file, infers HTTP methods, groups by resource, and cross-references your request validation rules to build realistic example payloads — no hand-crafting required.
The output is a valid .json file you can import straight into Postman:
{
"info": { "name": "My API", "schema": "...postman_collection.json" },
"item": [
{
"name": "Products",
"item": [
{ "name": "List products", "request": { "method": "GET", "url": "{{base_url}}/api/products" } },
{ "name": "Create product", "request": { "method": "POST", "body": { "mode": "raw", "raw": "{\"name\": \"...\", \"price\": 0}" } } }
]
}
]
}
You can also ask Claude to generate an Insomnia export format, or add pre-request scripts for token refresh if your API uses short-lived JWTs.
Your route file is the source of truth — generate your API collection from it, not the other way around.
Log in to leave a comment.
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.
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.
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.