Govern code at AI speed.
CloudAEye reviews changes for bugs, security risks, and maintainability. Get findings with code context and suggested fixes in Claude Code or your GitHub, GitLab, and Bitbucket pull requests.
50 free reviews per month for individual developers. Plan details
Focus attention on defects worth fixing.
User input may be undefined before accessing profile.
src/services/user.ts
async function loadUser(id: string) { const user = await db.users.find(id);- return user.profile.name;+ if (!user) throw new Error('Not found'); return user.profile.name;}Review the behavior, the boundaries, and the maintenance cost of a change. Each finding should help a developer decide what to fix and why.
Look for logic errors, missing edge cases, unsafe inputs, and failure handling.
For example: A missing database record reaches a property access without a null check.
Identify duplicated behavior and abstractions that add complexity without a useful boundary.
For example: Two generated helpers format the same value, leaving two places to fix the next bug.
Review access controls, secrets, and unsafe data flows across applications, LLMs, agents, and MCP tools.
For example: A query accepts a record ID but never checks the authenticated tenant.
Read the change alongside related callers, contracts, and tests, rather than treating the diff as the whole system.
For example: A return-type change also affects a caller in another file.
Find issues while the work is fresh, bring requirements into the review, and verify the correction before merging.
In Claude Code, inspect the pending diff for essential issues or run a broader review before opening the pull request.
Request a review in the PR or configure automatic reviews. Include Jira or GitHub issue references to check whether the change completes the requested work.
Use the finding's location, explanation, and suggested fix to make the correction. Test the failure path and review the updated change.
Apply your standards, learn from feedback, and keep reviews consistent.
Write repository-specific instructions, such as requiring tenant-scoped queries in API handlers.
Review and save rules proposed from selected past PRs. Use developer feedback to refine future reviews.
Select from 75+ checklist items. Start with global settings, then override them for individual repositories.
web-app: shared baseline with UI-specific review rules.
Review feedback and merge enforcement serve different purposes. Set each checklist item's mode to match your team's policy.
Keep the issue visible without making this checklist item a merge blocker.
A failed check can block merging when your repository host's required checks or branch restrictions are configured. Host plan requirements apply.
Code findings are one part of review. Review Intelligence also helps explain the change, assess its wider impact, and direct human attention.
Compare the PR with established design patterns, identify dependencies that cross layers, and explain changes by their role in the system.
Architecture reviewGet a structured overview of changed files, sequence diagrams, review effort, and related work. Configure the sections your team needs.
PR walkthroughsSee priority scores with reasons, using signals such as business impact, risk, complexity, and urgency to decide what needs attention first.
PR prioritizationUse directory ownership to identify qualified reviewers. Route sensitive changes to lead maintainers and balance other reviews across knowledgeable team members.
Reviewer assignment
Claude Code
cloudaeye:inspect
cloudaeye:review
/check_task [#42]
@cloudaeye /inspect
@cloudaeye /review
@cloudaeye /review [#42]
Connect a repository. Leave a review comment.
