VibeControls
Ask AI
Vibes3 illustrations

GitOps, Living Docs and Quality Scorecards

See a project's repository activity, its compiled documentation and a weighted quality score side by side, inside the vibe itself.

These images are illustrations of the concept, not screenshots of the actual product.

Overview

A vibe in VibeControls is a project context: the repository, environment, bound agents and notes for one piece of software. This concept extends the vibe with three views that answer questions a team asks about a project every week: what is changing in the code, where the current documentation lives, and whether the service is healthy enough to ship. Instead of hopping between a Git host, a wiki and a separate quality dashboard, the design keeps all three a tab away from the rest of the project.

The GitOps view is designed around a connected Git provider, chosen from a provider menu with Refresh and Add Provider actions beside it. Cards summarize the repository, with its visibility, default branch, license, star and fork counts and last sync time, alongside recent commit activity with top contributors, open pull requests in open and draft states, an activity chart and recent CI pipeline runs. A small sub-navigation switches between repository stats, CI pipelines and a Git view.

The Docs view treats documentation as something the project builds rather than a wiki that drifts. A page tree with nested folders for architecture and runbooks sits next to the rendered page, and the header shows a revision number, a published state and how long the last build took. Actions let a team edit a page, compile the docs again, copy a link, share the site or open it full screen.

The Scorecard view turns quality into one weighted score out of 100. Each metric card, covering areas such as test coverage, SLO compliance, incident count, security, CI/CD health, availability and open pull requests, shows its current value against a target, whether higher or lower is better, its weight and a passing, warning or idle state. A metric that misses its target is called out with a short recommendation. A side panel compares the project's score with other services in the workspace, and an alert history table with export sits below.

Together these views give engineering leads and platform teams a living record of each project, next to the vibe's overview and notes and connected to the software catalog and the fleet's health views.

What this concept shows

  • Repository summary card with visibility, default branch, license, stars, forks and last sync time
  • Commit activity with a top-contributors list and time since the last push
  • Open pull requests and recent CI pipeline runs with open and draft states
  • Docs site with a nested page tree, revision number, published state and build time
  • Compile Docs, Edit, Share, Copy Link and full-screen actions for the documentation
  • Overall score out of 100 built from weighted metric cards with targets and direction
  • Passing, warning and idle states per metric, with a recommendation on the metric that misses its target
  • Workspace comparison list and a 30-day alert history with severity pills and export

How it works

  1. Open a vibe and switch to its GitOps tab to pick, refresh or add a Git provider.
  2. Review repository stats, recent commits, top contributors, open pull requests and CI runs.
  3. Move to the Docs tab to browse the page tree and read the rendered documentation.
  4. Edit a page or select Compile Docs to publish a new revision, then share it or copy its link.
  5. Open the Scorecard tab to check the overall score and each weighted metric against its target.
  6. Compare the project with other services in the workspace and review or export recent alerts.

Who it's for

  • Engineering managers and tech leads
  • Platform and DevOps engineers
  • Service owners preparing releases
  • Site reliability engineers
  • Developers onboarding onto a project

Illustrations

3 illustrations of this concept. Select one to view it full size.

Vibe GitOps Repository Stats

The GitOps tab gathers repository stats, contributors, pull requests and CI runs for one project.

This illustration shows the GitOps tab of a sample payments service vibe, with Vibes selected in the left navigation and a breadcrumb leading from the workspace to the project. A tab row across the top includes Overview, Pipelines, GitOps, Events and About. Beside the GitOps heading sit a GitHub provider menu, a Refresh button and an Add Provider button, and a small sub-navigation offers Repo Stats, CI Pipelines and Git UI. The main area is a grid of cards: a repository card with a private badge, default branch, license, star, fork and watcher counts and a last-synced time; an Activity card with a sample commit total, top contributors and time since the last push; a Pull Requests card listing open and draft requests with authors and ages; a Status card marked online with a small bar sparkline; a two-series activity bar chart; and a CI Pipelines card listing recent runs.

Compiled Project Documentation

Project docs are built, versioned and published from inside the vibe.

This illustration shows the Docs tab of a vibe. The Documentation panel header carries a revision badge, a green Published status and the time the last build took. Along the right of the header are Share, Copy Link, Open Full Screen and Edit buttons, a highlighted Compile Docs button with a refresh icon and a settings control. On the left, a Pages list with an add button holds Introduction, which is selected, Getting Started, an Architecture folder with ledger and webhook pages, API Reference, a Runbooks folder with on-call and incident response pages, and a Changelog. The right side renders the selected page, with heading-level markers beside a title, a short summary of the sample service and an Architecture section. The design envisions documentation that is compiled like code and read like a site, living next to the project it describes.

Weighted Quality Scorecard

Weighted metrics roll up into one score, with a comparison across the workspace and recent alerts.

This illustration shows the Scorecard tab of a vibe, beside Overview, Sessions and Notes tabs. The header holds a Gold tier badge, a trend indicator, Share and refresh buttons and an Add Metric action. A large Overall Score card shows a sample score of 82 out of 100. Seven metric cards follow: test coverage, SLO compliance, incident count, security score, CI/CD health, service availability and open pull requests. Each shows its current value against a target, whether higher or lower is better, its weight, a progress ring and bar, and a Passing, Warning or Idle pill. The incident count card is outlined because it misses its target, with advice to reduce open severity-two incidents before release and a small trend line. A side panel compares service scores across the workspace, and an Alert History table for the last 30 days lists times, severity pills, messages and IDs, with a date range picker and Export.

Topics

  • project GitOps dashboard
  • repository activity overview
  • pull request and CI status
  • living documentation site
  • docs as code publishing
  • service quality scorecard
  • engineering scorecards
  • weighted quality score
  • SLO compliance tracking
  • internal developer platform scorecards

Related concepts

All VibeControls concepts
Get started freeBrowse all concepts

We use cookies for essential site functions and, with your consent, for analytics to improve VibeControls. We don't use advertising or cross-site tracking cookies. See our Cookie Policy.

Preferences