AI Code Review Dashboard

AI Code Review Dashboard is a desktop-first workspace for reviewing GitHub pull requests with a mix of heuristics, structured analysis, and optional LLM-generated summaries. The repository combines a FastAPI backend, a Next.js dashboard, and a Tauri shell that packages the app as a Windows desktop executable.

The packaged desktop app is currently branded in-window as Review Command Center, but the repository is organized and documented around the AI Code Review Dashboard project name for open-source and portfolio use.

Features

• GitHub OAuth sign-in and repository sync
• Pull request snapshotting, analysis history, and dashboard metrics
• Static, security, and architecture heuristics for changed files and diffs
• Optional AI-generated summaries and structured findings
• JSON and Markdown export support plus GitHub publishing hooks
• Desktop packaging with a local backend sidecar for Windows builds

Tech Stack

• Backend: Python 3.11, FastAPI, SQLAlchemy, SQLite or Postgres, optional Redis
• Frontend: Next.js 15, React 19, TypeScript, Tailwind CSS, React Query
• Desktop: Tauri 2, Rust, PyInstaller sidecar packaging
• Quality: Ruff, Pytest, ESLint, TypeScript type-checking
• CI: GitHub Actions via .github/workflows/ci.yml

Repository Layout

.
|-- backend/                FastAPI API, analysis pipeline, worker, tests
|-- frontend/               Next.js app plus Tauri desktop shell
|-- docs/                   Deployment and release notes
|-- scripts/                Repository-level helper scripts
|-- .github/workflows/      CI automation
`-- README.md

Quick Start

1. Backend

cd backend
python -m venv .venv
.venv\Scripts\activate
python -m pip install --upgrade pip
pip install -e ".[dev]"
copy .env.example .env.local
make dev

Default API URL: http://localhost:8000/api/v1

2. Frontend

cd frontend
npm ci
copy .env.example .env.local
npm run dev:web

Default web URL: http://localhost:3000

3. Desktop Shell

cd frontend
npm run desktop:dev

The desktop dev script starts the backend automatically if http://localhost:8000/api/v1/health is not already healthy.

Environment Variables

Repository-safe examples live in:

• backend/.env.example
• frontend/.env.example

Backend variables you will typically need:

• SECRET_KEY
• DATABASE_URL
• REDIS_URL
• GITHUB_CLIENT_ID
• GITHUB_CLIENT_SECRET or GITHUB_CLIENT_SECRET_FILE
• GITHUB_APP_ID
• GITHUB_APP_PRIVATE_KEY_FILE
• GITHUB_WEBHOOK_SECRET
• OPENAI_API_KEY
• OPENAI_MODEL

Frontend variables you will typically need:

• NEXT_PUBLIC_API_BASE_URL
• AICR_DESKTOP_API_BASE_URL for packaged desktop overrides

For local development, prefer .env.local files. For deployed environments, prefer platform secret stores or environment variables instead of committed .env files.

GitHub OAuth and App Setup

GitHub OAuth App

Use a GitHub OAuth App for user sign-in.

1. Create an OAuth App in GitHub.
2. Set the callback URL to http://localhost:8000/api/v1/auth/github/callback for local development.
3. Put the client ID in GITHUB_CLIENT_ID.
4. Put the client secret in GITHUB_CLIENT_SECRET or, preferably, point GITHUB_CLIENT_SECRET_FILE at a local file outside version control.

Optional GitHub App

Use a GitHub App if you want to publish summaries, inline comments, or checks back to pull requests.

1. Create a GitHub App with access to pull requests, contents, checks, metadata, and webhooks.
2. Download the private key and store it outside the repository when possible.
3. Set GITHUB_APP_ID, GITHUB_APP_PRIVATE_KEY_FILE, and GITHUB_WEBHOOK_SECRET.
4. Install the GitHub App on the repositories you want the dashboard to analyze.

Build and Release

Web Build

cd frontend
npm ci
npm run build:web

Static export output: frontend/out

Windows Desktop Build

cd backend
pip install -e ".[desktop]"

cd ..\frontend
npm ci
npm run desktop:build

Important output locations:

• Static web assets: frontend/out
• Intermediate PyInstaller sidecar: backend/.desktop-build/dist
• Bundled sidecar copy: frontend/src-tauri/binaries
• Windows installer and desktop bundle: frontend/src-tauri/target/release/bundle/nsis

You can also use scripts/release.ps1 to run the standard Windows release flow.

Screenshots

Suggested screenshot set for a public repository:

• Dashboard overview
• Repository and pull request queue
• Pull request detail workspace
• Analysis results with findings filters
• Settings and integration status

Troubleshooting

• GitHub is not connected: confirm the OAuth app callback URL and client secret configuration.
• GITHUB_APP_PRIVATE_KEY_FILE errors: verify the file exists and the path is readable by the backend.
• OPENAI_API_KEY errors in desktop or production mode: set LLM_ENABLED=false or provide a valid key.
• cargo or rustc missing: install Rust from https://rustup.rs/ before running npm run desktop:build.
• Desktop build cannot find PyInstaller: run pip install -e ".[desktop]" in backend first.

Additional Docs

• Deployment guide
• Release notes and artifact locations
• Contributing guide
• Security policy

Notes for Publication

• A live GitHub Actions badge is intentionally not hard-coded yet because this workspace is not currently attached to a GitHub repository remote.
• Generated folders, databases, desktop binaries, logs, and local secret files are ignored by design and should not be committed.