Generate an OpenAPI Spec from Your Existing Routes
If your API predates your documentation, ask Claude to reverse-engineer a full OpenAPI spec from your route files.
@routes/api.php @app/Http/Controllers/Api/
Read these files and generate a complete OpenAPI 3.0 spec in YAML covering
all public endpoints — include request parameters, request bodies, and
response schemas inferred from the controller logic and Form Requests.
Claude reads your controllers, infers validation rules from Form Requests or inline validate() calls, and produces a well-structured YAML spec you can paste straight into Swagger UI, Stoplight, or Redoc.
paths:
/api/users/{id}:
get:
summary: Get a user by ID
parameters:
- name: id
in: path
required: true
schema:
type: integer
responses:
'200':
description: User found
'404':
description: User not found
Pass the generated spec back to Claude and ask it to add missing error responses, authentication schemes, or example payloads. It can also generate a Postman collection from the same spec.
Going from zero documentation to a working OpenAPI spec in minutes beats writing it from scratch.
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.