Four days, zero lines: the AI force multiplier with GitHub Copilot
Jeff Doolittle, Distinguished Engineer and Principal Architect at Trimble, presents the governance work in this GitHub Universe 2026 session. He explains how automation and custom Copilot prompts helped address a backlog of 436 repositories while keeping architectural decisions and human judgment central.
From compliance backlog to automated governance
The session follows the development of OSS overseer, a repository governance system built with GitHub Copilot in four days without Doolittle manually writing a line of code. It addresses deferred organizational debt: compliance work that accumulates across repositories and creates friction when teams eventually need to resolve it.
The approach combines:
- GitHub Actions to automate governance work and enforce remediation lifecycles.
- Custom Copilot prompts to help developers resolve compliance issues through self-service remediation.
- Reversible enforcement to build trust in the system.
- Human judgment to guide architecture and policy rather than treating code generation as the goal.
Doolittle reports achieving 100% compliance across the repositories. The broader lesson is to use AI-assisted development alongside deliberate architectural design: automate repeatable work, reduce the effort required to remediate issues, and preserve human responsibility for decisions.
Session chapters
- 00:00 — The 436-repository compliance backlog: The scope of the governance problem.
- 01:23 — The friction of deferred organizational debt: How accumulated obligations affect developer work.
- 02:29 — Building OSS overseer with GitHub Copilot: The four-day implementation effort.
- 04:13 — Prioritizing human judgment over code generation: The role of architectural decisions.
- 05:25 — Designing trust and reversible enforcement: Enforcement that can be reversed.
- 06:40 — Lowering friction with self-service remediation: Helping developers address issues themselves.
- 08:38 — Achieving 100% compliance across repositories: The reported outcome.
- 10:29 — Turning automation into a force multiplier: Using automation to extend engineering capacity.
- 12:14 — Architectural strategy for eliminating technical debt: Applying the approach to wider organizational debt.