code-review

Review Insites Liquid templates by analyzing changed files for XSS, injection, and convention violations. The code review process flags quality, security, and architecture problems in pages, partials, and forms, returning prioritized findings with actionable remediation steps.

Automate Insites code review by inspecting changed files in a pull request workflow. The review identifies missing tests, duplication, i18n gaps, and unsafe API usage, then classifies findings by severity to deliver actionable remediation guidance for application correctness and maintainability.

Yes, the code review process checks Insites GraphQL files and forms for data exposure and auth gaps. It validates that these files follow platform architecture conventions while flagging security vulnerabilities and unsafe API usage during the changed-file review workflow.

Yes, you can catch missing test coverage and i18n gaps during an Insites code review. The review surfaces missing tests, duplication, naming issues, and internationalization content gaps with clear severity classifications to ensure application maintainability.

Severity classifications applied to Insites code review findings include critical issues, warnings, and suggestions. Findings cover security vulnerabilities, architecture violations, and quality concerns, providing reviewers with prioritized, actionable remediation guidance for each changed file.

You need to enforce Insites platform conventions during a code review whenever changes involve pages, commands, partials, forms, or GraphQL files. The review validates architecture compliance and flags convention violations to prevent quality and security issues from shipping.