// 333 tips tagged "advanced"
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.
When you have a written specification — a PRD, a requirements doc, a technical design, or even detailed meeting notes — pipe it directly into Claude Code as context. Claude reads the full document, understands every requirement, and implements the feature exactly as specified instead of you re-explaining it piece by piece.
Claude can read your application code — the jobs, queues, API endpoints, scheduled tasks, and critical business logic — and generate monitoring rules that alert on the things that actually matter: failed payments, queue backlogs, stale cron jobs, error rate spikes, and slow endpoints, all tailored to your real system.
Use the --agent flag with custom markdown files in .claude/agents/ to launch purpose-built Claude sessions with restricted tools and scoped system prompts.
Use /batch to fan out large-scale code changes across parallel worktree agents that work without conflicts.
Most code is written for the happy path — everything works, data exists, APIs respond, and inputs are valid. Tell Claude to read your code and add error handling for every failure mode — null values, network timeouts, invalid data, missing config, and unexpected states — so your app degrades gracefully instead of crashing.
Every language evolves — callbacks become async/await, class components become hooks, jQuery becomes vanilla JS, and var becomes const. Tell Claude to read your legacy code and upgrade it to modern patterns, one module at a time, while keeping the behavior identical and the tests passing.
When you need to make the same change to 20 files — add a trait to every model, wrap all API responses in a consistent format, add logging to every controller, or update an import path everywhere — describe the change once and tell Claude to apply it across every matching file. One prompt, twenty edits, zero copy-paste.
Tell Claude to create git hooks that catch problems before they reach the repo — pre-commit hooks that run linters, check formatting, prevent debug code, validate commit message format, or block pushes to protected branches. Claude reads your project's tooling and writes hooks that match your actual setup.
Before refactoring code that looks wrong or unnecessary, tell Claude to check git blame and the commit history to understand why it was written that way. What looks like a bug might be a deliberate workaround — and Claude can find the original commit message that explains the reasoning before you accidentally undo it.
When a page takes five seconds to load or an API endpoint times out under load, tell Claude which route is slow and it traces the entire code path — controller, services, queries, loops — identifying N+1 queries, redundant computations, missing indexes, and cacheable operations, then fixes each bottleneck.