review

Run the review workflow on your feature branch; it fetches the latest base branch, computes the full diff, and applies a two-pass checklist covering critical issues like SQL safety and race conditions plus informational findings like test gaps and dead code.

It catches SQL injection via string interpolation, TOCTOU race conditions, unvalidated LLM output written to databases, incomplete enum handling across consumers, N+1 queries, XSS via unsafe HTML rendering, and scope drift from the stated plan.

Yes, the workflow detects the hosting platform from the git remote URL and uses glab for GitLab or gh for GitHub, with a git-native fallback when neither CLI is authenticated.

Yes, mechanical fixes like dead code removal, magic number extraction, and missing eager loading are applied automatically. Riskier findings such as security issues, race conditions, and large fixes are batched into a single question for human judgment.

It fetches Greptile line-level and top-level PR comments, classifies each as valid, already fixed, false positive, or suppressed based on project history, then posts evidence-based replies using tiered templates.

Most checks analyze only the diff, so issues in untouched code are missed except for enum completeness, which greps and reads consumer files outside the diff. It also requires a diff against the base branch and stops if none exists.