Reviews & automations

Automatic PR checks

When you open or update a pull request in a repository connected to gjalla, an automated architecture analysis runs. The results appear as GitHub check runs that show how the PR affects your system’s architecture, capabilities, and compliance with design principles.

This is powered by Change Reviews: evidence-backed records of system evolution. Each enabled evaluator runs as a separate GitHub check, so you can see and gate on each domain independently.

Configuring what runs

Which evaluators run, when they run, and which ones block a merge is all configured on the Automations page in your workspace. Most checks start as advisory. You see the signal first, and flip a check to blocking once you trust it.

Reports

Independent of Change Review.

Email Digest (Startup) sends a weekly summary of recent change impact and findings that may need attention. It runs on its own schedule; turning Change Review off does not silence the digest.

Automatic doc/context updates on merge (Startup) refreshes project state and documentation after each merge so the platform context (and your agents) always reflect the current system.

What the check shows

Example check output

🏛️ Architecture elements

• ✨ Added NotificationPreferencesService: new service for managing user notification preferences
• 📝 Modified UserAPIRouter: added GET and PUT endpoints for notification preferences

🎯 Capabilities

• ✨ New: User Notification Preferences Management
• 📝 Enhanced: User Settings Management

⚠️ Rule violations

None detected ✅

View complete example PR review

Benefits

• Reduce review burden: automated analysis surfaces key architectural changes, letting reviewers focus on logic and design
• Catch architecture drift early: see when implementation diverges from intended architecture before merging
• System-level review: understand impact beyond file changes; see how components, relationships, and capabilities evolve
• Maintain compliance: automatically check PRs against your documented decisions, principles, and invariants

Setup

PR reviews run through the gjalla GitHub App. There are two ways to connect it, depending on whether you already have a gjalla project:

New project

Create a new project and select the GitHub onboarding flow. You’ll install the GitHub App and connect a repository as part of the setup wizard.

Existing project

Open your project workspace and navigate to Configuration in the sidebar, then click “Install GitHub App.” If your organization requires admin approval for GitHub App installations, gjalla tracks the pending request and activates automatically once approved.

Defaults work out of the box: open or update a pull request and gjalla runs the enabled evaluators, posting each as its own check. For best results, also install the gjalla CLI so your coding agents write attestations with each commit.

Re-running analysis with @gjalla redo

To re-run the architecture analysis on a PR, leave a comment containing:

@gjalla redo

gjalla reacts with an 👀 emoji to acknowledge the request, then runs a fresh analysis and posts a new comment with the updated results. Repository owners, organization members, collaborators, and contributors can trigger it. Use it after pushing fixes for rule violations, after updating project rules, or any time you want a fresh analysis.

PR change history

Every PR analysis is saved as a change receipt. To see the full history of changes to your system over time, open your project workspace and navigate to Activity → PR Reviews.

Full analysis in gjalla

The GitHub check shows a summary. Click through to gjalla to see the complete Change Review with detailed evidence, impact analysis, and full context.