code-review

To review local code changes, inspect your workspace files and optionally run targeted terminal commands to validate behavior. This produces a prioritized summary flagging correctness, security risks, reliability, and maintainability issues with exact file paths and suggested fixes.

Yes, you can use terminal commands to validate behavior during static analysis. When terminal access is enabled, the review process runs focused commands like git diffs and targeted test executions to confirm code behavior and assess patch risks.

The best way to assess maintainability improvements is to inspect the local project structure, read relevant files for context, and execute focused tests. This generates an actionable outcome prioritizing correctness, security, reliability, maintainability, and style with concise fix recommendations.

Code review works directly with pull-request-like workflows and git diff patches. It evaluates patch assessment and bug risk analysis by inspecting workspace files, validating behavior with terminal commands, and providing prioritized, correctness-first findings with exact file paths.

To get an actionable summary with fix recommendations for your patch, review the local changes in your project. The process produces a prioritized summary that flags correctness first, then security, reliability, maintainability, and style with exact file paths and concise fixes.

Without terminal access, automated code review is limited to static analysis of workspace files and cannot run targeted test executions or commands to validate behavior. It will still produce prioritized findings for correctness, security, and maintainability based on file inspection alone.