Claude Code Prompts

give me an overview of this codebase. focus on:
- directory structure and key entry points
- tech stack and major dependencies
- architecture patterns used

trace the complete request flow for user login.
Start from @src/pages/Login.tsx, follow through API calls,
middleware, and database queries. Draw the dependency chain.

find all API endpoints in this codebase. for each one list:
- HTTP method and path
- auth requirements
- request/response types

git diff main | claude -p "review this diff for bugs,
security issues, and missing edge cases.
be specific about line numbers."

audit @src/api/ for security issues:
- SQL injection / NoSQL injection
- XSS vectors in response data
- missing auth checks on endpoints
- secrets or keys in source code
- unsafe deserialization

review my staged changes (git diff --cached) for:
- potential bugs and race conditions
- missing error handling
- breaking API changes
- test coverage gaps
then suggest a PR title and description.

/advisor opus
review the current plan and identify the strongest objection.
Only call out issues that would change the implementation.

write failing tests first for this feature:
[describe feature]

Put tests in @src/__tests__/. Use the existing test patterns
in that directory. Then implement the feature to make
all tests pass. Do not modify the tests after writing them.

refactor @src/utils/legacy-parser.ts:
- reduce cyclomatic complexity
- extract pure functions
- add TypeScript types where missing

run the existing tests after each change to ensure
nothing breaks. commit after each successful refactor.

create a pr for the current changes.
include a summary of what changed and why.
link any related issues.

I'm getting this error in production:
[paste error/stack trace]

Trace from @src/server.ts through the call chain.
Identify the root cause and suggest a fix with a test.

tail -100 /var/log/app.log | claude -p "summarize errors,
group by type, and suggest fixes for the most frequent ones"

we just fixed a null check bug in @src/checkout.ts.
scan the entire codebase for similar patterns where
we access properties without null/undefined guards.

look at @prisma/schema.prisma and create a migration
that adds a "preferences" JSONB column to the User table.
generate the migration file and update the TypeScript types.

the CI pipeline is failing. look at @.github/workflows/
and the latest error output below:
[paste CI error]

diagnose and fix the issue.

ultracode: inspect every API route for missing auth checks.
Use separate workflows for discovery, verification, and patching.
Before editing, report the risk categories you found.

/goal migrate the test suite to vitest until npm test passes
and no imports reference the old jest setup.