Database Access Audit: Safety & Performance

Database code can look correct while updating the wrong records or making too many queries. Get a prioritized review that shows where data access is risky, what supports each finding, and what to fix first.

What it does

• Finds data risks: Reviews account isolation, transactions, concurrent operations, and bulk changes.
• Checks performance: Investigates repeated queries, N+1 access, large batches, and index support.
• Explains findings: Provides code locations, supporting evidence, confidence, and practical fix recommendations.
• Checks proposed shortcuts: Assesses whether bulk operations could skip required validation, events, or other business behavior.

How it works

1. Share your repository and name the service, endpoint, job, or area to review.
2. Request an audit, or explicitly ask for code fixes.
3. Receive a scoped report with priorities, uncertainties, and suggested validation.
4. Use the recommended fix order to plan changes and tests.

Works with

Repository code, database schemas, migrations, tests, and available query logs. It does not assume a particular language, framework, ORM, or database engine.

Why use this skill

Spend less review time chasing suspicious-looking code that is actually safe. Findings are checked against surrounding code and available evidence, with data correctness considered before performance improvements.

Use cases

• Review a bulk update before release.
• Investigate repeated queries in an endpoint.
• Check account isolation in shared database tables.
• Assess transaction safety in a background job.

Known limitations

The default review is static and read-only. Runtime behavior and performance may remain uncertain without logs, tests, or other supporting evidence.