Ask Claude to Set Up Structured JSON Logging
Plain text logs are hard to search and impossible to parse in a log aggregator. Structured JSON logs give you queryable fields and context on every line — and Claude can set the whole thing up.
Set up structured JSON logging in my Express app using Pino.
Add request middleware that includes: request_id, method, path, status_code,
response_time_ms, and user_id (if the request is authenticated).
Claude will install the right library, configure log levels per environment (debug locally, info in production), and add the middleware. For Laravel:
Configure Laravel's logging stack to output JSON in production.
Add a custom processor that includes the authenticated user ID,
request ID (from X-Request-Id header), and app version in every log entry.
You can also route logs to external services:
Add a Laravel logging channel called 'slack_errors' that sends
ERROR and CRITICAL level logs to Slack using the LOG_SLACK_WEBHOOK_URL env var.
Configure the 'stack' channel to use both 'daily' and 'slack_errors'.
Claude understands log channel stacking, tap processors, and formatter configuration — the parts where the docs always send you in circles.
Structured logs are searchable, alertable, and production-ready — set them up once with Claude.
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.