Loading...
We kept reconfiguring our own extension every time we switched between our open-source repos and client work, so we built profiles to stop doing that. Each workspace gets its own AI model, API key, prompt, and rule set — and the switch happens automatically from the VS Code status bar when you open a different project.
Here is the problem we kept hitting ourselves: your open-source side project wants Claude API with relaxed rules, your work monorepo needs strict security scanning, and your client insists on Gemini because they mandate Google Cloud for everything.
Without profiles, you reconfigure settings every time you switch projects. API keys, model selection, custom prompts, security rules — all manual.
With profiles — one click from the status bar.
The active profile is always visible. Click to switch instantly.
A profile is a complete snapshot of your Git AutoReview configuration. Everything switches together — no partial states.
Create profiles for any workflow. Here are four common setups.
Bind profiles to workspace folders. The right config activates automatically when you open the project.
Different clients need different review setups. Keep client API keys, Jira instances, and coding standards separate. Switch when you switch projects.
Share strict review settings for production repos, relaxed settings for prototypes. Team lead configures once, everyone switches with one click.
Your open-source project uses Claude API with relaxed rules. Your work monorepo uses Claude CLI Agent with strict security. Auto-switch when you open the workspace.
Each profile has its own encrypted API keys. Your personal keys never mix with work keys. Copying a profile never copies API keys.
We checked. CodeRabbit, Greptile, Qodo, Bito — none of them offer named review profiles with one-click switching and workspace auto-binding. Review Profiles are unique to Git AutoReview.
Create profiles for every workflow. Switch in one click. Available on Developer and Team plans.