Orbit Impact Guardian

• 

  MR readiness report: risk score, affected components,blockers,test plan, suggested reviewers, and an Orbit evidence trace — all in one view.

• 

  Safety by default: dry-run comments, risk thresholds, data source, and theme — the Guardian reports, it never merges or posts on its own.

• 

  Pick a project: each card shows open MRs, issues, pipeline health, and whether GitLab Orbit is ready — then open the Guardian.

• 

  Same engine in the terminal: Orbit Local mode queries a real indexed Knowledge Graph — schema-verified, with evidence checked into the repo.

• 

  Live GitLab Duo flow output: Orbit Impact Guardian posts the MR readiness report with score 78/100, High risk, and Blocked status.

Inspiration

What it does

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for Orbit Impact Guardian

Inspiration

Every reviewer asks the same questions before opening a merge request: what does this change affect, what could break, what should be tested, who knows this code, and is it safe to merge? Today those answers require manual digging through diffs, imports, pipelines, security state, and git history. Diff-only AI can sound confident, but without graph context it is guessing.

What it does

Orbit Impact Guardian turns that review ritual into an evidence-backed workflow. It uses GitLab Orbit, the GitLab Knowledge Graph, to gather blast radius, reviewer signals, pipeline risk, and security context, then applies one transparent risk rubric shared across the Duo agent, flows, skill, CLI, and web console. The output is a structured readiness report with affected components, blockers, recommended tests, suggested reviewers, and an Orbit Context Trace showing what evidence was found and what is still missing.

How we built it

The project includes a custom Duo agent definition, MR-readiness and issue-impact flow YAML, an installable Codex skill, a Python CLI, API-backed web console, GitLab comment preview, GitLab CI, and a real GitLab Orbit Local integration. Orbit Local was built from source, indexed this repository, and queried the verified schema tables gl_definition and gl_imported_symbol.

Meaningful GitLab Orbit usage

Orbit Impact Guardian uses Orbit Remote query builders for blast radius, reviewer candidates, failed pipelines, vulnerabilities, and recent merge requests. It also has a verified Orbit Local mode that reads real graph data from this repository and clearly labels missing evidence instead of inventing it.

Impact

Review triage that normally takes 20-30 minutes becomes a repeatable pre-review guardrail. Developers get a clear readiness verdict before a maintainer spends time in the diff, and reviewers can trust the report because missing evidence is stated plainly.

Current submission status

The public GitLab repository, CI pipeline, demo video, agent definition, flow YAML, skill, CLI, and web console are ready. The dedicated GitLab Showcase project is live, the public custom agent and public MR-readiness flow are enabled, and corrected flow session 4410707 posted the Orbit Impact Guardian Report on test MR !1. The report honestly records missing Orbit graph tools in the flow runtime while the repository includes verified Orbit Local graph evidence from this codebase.

Built With

• css
• edge-tts
• ffmpeg
• gitlab-ai-catalog
• gitlab-ci/cd
• gitlab-duo-agent-platform
• gitlab-orbit
• html
• javascript
• pytest
• python