code-review

You can perform a comprehensive code review by submitting pull request changes for analysis. The review evaluates design, quality, correctness, security, performance, testing, and documentation, providing structured, severity-based feedback with actionable fix suggestions.

Automated code review identifies OWASP Top 10 vulnerabilities by checking submitted code against detailed security checklists. It reports findings with severity levels and specific file or line references to ensure code is secure and maintainable.

Yes, the code review process is language-agnostic, meaning it analyzes design, quality, correctness, and security across different programming languages without requiring language-specific configurations or dependencies.

The best way to get structured feedback is to trigger a code review on your pull request changes. The review outputs structured findings categorized by severity, detailing design, security, and performance issues with actionable fix suggestions and file references.

Yes, code review checks documentation and testing coverage alongside security. The comprehensive review process evaluates code across seven dimensions including testing and documentation, ensuring maintainability and quality assurance across the entire codebase.

You should not use an automated code review skill for general coding queries or writing new code from scratch. It is specifically intended for reviewing existing code changes, such as providing feedback on pull requests, rather than generating new code snippets.