Reviews in GitHub
Connect selected repositories, choose the reviewer profile, and inspect findings against the pull-request commit. Your normal CI and maintainer merge rules still apply.
MANAGED REVIEW · PROJECT MEMORY
Keep pull-request reviews moving. Keep your project context.
For small teams shipping with AI: Redgold helps set up and operate your review workflow, with repository rules, retained project context, and spending controls. Keep the findings in GitHub and the decisions with your project.
A review workflow we help you run.
Context for the next change
Keep repository instructions and relevant project decisions available to agents. Configure project memory during onboarding and check which context a review actually used.
Setup and operating help
We help configure access, review behavior, and usage limits, then investigate incomplete runs with you. Start with one repository and an agreed scope.
Choose the review depth and the spending limit.
Use Economy, Standard, or Deep review profiles. Set the number of independent reviewers separately from the number of review rounds allowed on a pull request. Begin with review-only behavior; enable fixer commits only when you want eligible corrections on the pull-request branch.
Set monthly repository automation and per-pull-request spending limits. These stop future model calls after recorded usage reaches the limit; calls already running and delayed accounting can exceed it. They are not a guaranteed cap on the complete bill. Confirm compute, model, and external provider charges during setup.
Start with a paid managed preview.
Request access with your project, approximate pull-request volume, and the part of review you want to improve. We discuss fit, the supported repositories, and the setup work before enabling automation.
We agree the paid scope, subscription, included usage, and any setup or additional usage charges before you buy. Public workspace plans are listed on Pricing; this request does not purchase a plan or promise an all-inclusive managed service at a listed workspace price.
The first milestone is a completed review on an agreed pull request, with visible findings, usage, and a maintainer’s assessment. We use that result to tune the workflow and decide whether ongoing use is worthwhile.
Built around an existing repository workflow.
Elusive uses Redgold for repository reviews and remote Linux CI. Our published workflow account describes a completed review, the context and review stages involved, and the operating lessons from that integration.
We have not published independently measured savings, review accuracy, or a customer revenue figure. Use the workflow account to understand the integration, then judge your own pilot by useful findings, completed reviews, total cost, and time spent maintaining it.
Keep useful context without assuming perfect recall.
A persistent workspace, saved conversations, repository files, and retrieved memory have different jobs. A reviewer still needs to inspect the current diff and check whether a saved decision applies. Stale context should be corrected rather than repeated as a rule.
During setup, agree what may be retained, which project owns it, and how to inspect or remove it. The offer does not promise that every previous conversation enters every review or that your project trains a private model.