review

Checking code style compliance before a pull request involves running a full branch review to catch style inconsistencies. This ensures the codebase remains clean, maintainable, and aligned with established best practices and style guides.

To run a code quality audit on recent repository changes, perform a quick style audit targeting recent changes. This validates code compliance against predefined style guides, detecting violations, warnings, and suggestions across the updated files.

Yes, you can automatically fix linting violations and style warnings detected during a code review. The review process includes an option for automated fixing to correct identified style violations automatically after checking files.

Yes, the code audit integrates with existing LSP configurations and linters. This integration allows it to effectively detect style violations, warnings, and suggestions across various scopes including directories, branches, and entire repositories.

Reviewing code for style guide violations supports multiple scopes including recent changes, specific commits, branches, directories, and entire repositories. This allows targeted checks or comprehensive full codebase audits depending on requirements.

Running a comprehensive code review across an entire repository identifies deep-rooted style inconsistencies and compliance violations that checking recent changes misses. It ensures the entire codebase adheres to established style guides and best practices.