Connect today's pull requests with engineering history and
production impact.
Trend and risk analysis
Understand author and team AI slop scores, bug history,
product-area stability, and production incidents.
cloudaeye:trends <pr#>
cloudaeye:trends <pr#> --verbose
Prioritized PR dashboard
Order the queue by priority score, with risk, complexity,
business impact, and a reason for each ranking.
cloudaeye:prioritize-prs
Assign human reviewers
Recommend a reviewer with relevant ownership, review
history, and incident experience, along with a suggested
review focus.
cloudaeye:assign-reviewer <pr#>
Prevent recurring production incidents
Bring lessons from previous production incidents into the
review of new changes.
Help, right in your terminal.
List all supported commands or get detailed usage and options
for a specific command.
cloudaeye:help
cloudaeye:help <command>
A merge decision. Not an endless to-do list.
Does the PR deliver the requested work? Is there a meaningful
issue that should stop it from shipping? CloudAEye connects issue
intent with severity-ranked findings to answer both.
Critical findings block approval. A clean PR can receive an actual
GitHub approval automatically. The goal is a clear outcome, not
another round of subjective changes.
Test name could describe the boundary case more precisely
Non-blocking improvement
APPROVAL ISSUEDAll required checks passed. Ready to merge.
A few things worth knowing.
Which issue trackers can I use?
Use Jira, GitHub, or GitLab with
cloudaeye:explain and
cloudaeye:create-issue. Explain also accepts an
issue URL. Tracking issues can be assigned to the person named
in the command.
What happens if Jira or the checklist is not configured?
The explain command detects missing Jira configuration and opens
its setup UI. The check command detects when a repository
checklist is not enabled and opens the UI to select checklist
items.
Can I turn review comments into follow-up work?
Yes. Use cloudaeye:create-issue with the comment
number, your issue tracker, and an assignee to create a tracking
issue in Jira, GitHub, or GitLab.
What does trend analysis include?
Author and team AI slop scores, recent bugs and incidents,
product-area stability, and related production incidents. Add
--verbose for a detailed breakdown, including risk
signals and a recommended human reviewer.