review-database-access

To check PHP code for direct mysqli calls during a code review, scan the modified files for direct database access methods. This Skill audits the code to identify low-level query calls and ensures database interactions adhere to established security boundaries.

Common database access boundary violations in PHP SQL code include direct mysqli usage, low-level SQL queries executed outside designated library directories, and the use of deprecated cursor APIs. Scanning for these legacy patterns ensures secure database interaction implementations.

To scan PHP files for unsafe SQL and legacy database patterns, run an automated audit on the changed code. This process detects direct mysqli usage and deprecated cursor APIs, verifying that all database access follows best practices and security boundaries.

You should audit your PHP code for database access violations after making database-related code changes. Running an audit on the modified files confirms no direct mysqli calls or unsafe SQL were introduced, ensuring adherence to access policies.

Yes, this code review tool checks for low-level SQL queries outside the lib directory. Scanning for database access outside designated library paths prevents security violations and enforces proper architectural boundaries.

Yes, you can use this to find deprecated cursor APIs in PHP database logic. The audit specifically targets these legacy patterns alongside direct mysqli calls to ensure all database interactions maintain security and maintainability standards.