SIGNAL

Inspiration

Every engineering team has a developer who keeps everything running. Reviews everyone's code. Unblocks colleagues. Fixes pipelines at midnight. Their commit count? Average. Their actual impact? Irreplaceable.

Metrics never see them. Managers never recognize them. Until they quit. Then everything breaks and nobody knows why.

SIGNAL was built for that developer.

What it does

SIGNAL reads the GitLab Orbit knowledge graph across 10 analytical layers and delivers personal engineering intelligence to every developer:

• Layer 1 - Personal Morning Brief: What matters to YOU today
• Layer 2 - Conway's Law Mirror: Where team structure has diverged from code structure
• Layer 3 - Invisible Work Revealer: Contributions that commits never show
• Layer 4 - Revert Prophet: MR revert probability before you merge
• Layer 5 - Bus Factor Calendar: Who leaving would break everything
• Layer 6 - Broken Telephone: Where product intent gets lost before code
• Layer 7 - Dead Reckoning: Roadmap vs actual code state
• Layer 8 - Career Mirror: Developer growth trajectory from the graph
• Layer 9 - Expertise Decay: Skills becoming obsolete as codebase evolves
• Layer 10 - Pressure Code Auditor: Code written under stress, never reviewed

One prompt. One brief. Every number is real.

How we built it

• SKILL.md - 700+ line Orbit intelligence engine teaching all 10 layers
• Custom GitLab Duo Agent - SIGNAL, available in the AI Catalog
• Automated Flow - 4-agent pipeline that posts a weekly briefing issue automatically
• Uses Orbit: Query Graph, Orbit: List Commands, GLQL, and GitLab API natively

Challenges we ran into

Orbit is new. The schema evolves. Half the battle was discovering what the graph could actually answer - and designing fallback patterns when it couldn't. The Orbit Beta tools (Query Graph, Invoke Command) are powerful but undocumented at the query level. We mapped them ourselves.

Accomplishments that we're proud of

SIGNAL ran against our own project and produced this finding:

"You're building a tool to reveal invisible contributors. Right now, you are the invisible contributor."

That line came from real data. That's the whole point.

What we learned

The most important signals in an engineering organization are never in the commit graph. They're in the space between commits - the reviews given, the colleagues unblocked, the fires quietly put out. Orbit can see that space. Nobody was looking.

What's next for SIGNAL

Continuous monitoring. SIGNAL running weekly across your entire organization, tracking layer scores over time, alerting when a mismatch gets worse, giving engineering teams the longitudinal health data they expect from application monitoring - but for the team itself.

Built With

• gitlab
• gitlab-duo-agent-platform
• gitlab-duo-flows
• gitlab-graphql-api
• gitlab-orbit
• glql
• rest