Rules-based scanners match syntax patterns; CloudThinker reads intent. It knows when code touches infrastructure — IAM policies, S3 permissions, database queries — and flags cloud-specific risks alongside logic bugs and vulnerabilities. Security and quality run in a single pass, so reviewers see one set of findings in the tools they already use.
How it works
- Detect — a developer opens a pull request on a connected repository. CloudThinker picks it up automatically.
- Gather context — Oliver reads the full diff, any Jira ticket linked in the PR description or branch name, and relevant Confluence documentation.
- Analyze — the review runs in parallel across security, quality, and cloud-infrastructure dimensions.
- Post findings — in-line comments land on the PR with exact line references, severity ratings, and remediation guidance.
- Track — when a linked ticket provides acceptance criteria, the review records a ticket-compliance verdict. When you push a fix, the next review verifies it, and every finding feeds the Leaderboard.
Legacy Code Review example showing a Jira ticket linked to a finding
What you can do
Get started
Set up code review
Connect your GitHub or GitLab repositories in under 5 minutes
Mention commands
Interact with CloudThinker directly from PR and MR comments
Convention rules
Keep reviews aligned with your team’s convention files and rules learned from past reviews
Leaderboard
Track team review activity and code quality improvements over time