GitLab repo standards board with one-click fix merge requests

Build me a repo standards board for GitLab that replaces the spreadsheet my platform team uses to track which projects are actually set up properly. The main view is a grid with one row per project and one column per standard we define inside the app, and each cell shows pass, fail, or not applicable at a glance, along with a link to any fix that is currently in flight.

Projects come from List User Projects, and Get a Project fills in the details each row needs: the default branch, the namespace or group path, visibility, description, topics and the web URL. Let me refresh the project list on demand and choose which projects belong on the board, since not every project the connection can see is one we care about. Group rows by team, defaulting to the project's group or namespace path, and let me override the team label for a project and store that override in the app.

The checklist itself is stored in the app so a platform engineer can edit it without shipping code. A rule has a name, a short description of why it exists, a severity, and a check type. Support these check types: a file exists at a path (CODEOWNERS, README, LICENSE); a file exists and its contents match or contain something (a .gitlab-ci.yml that includes our security scan job, a Dockerfile whose FROM line pins one of an approved list of base images, a shared CI template include that is on the current version); and a project setting returned by Get a Project matches an expected value, such as the default branch name or the merge settings. Give me a rules page where I can add, edit, reorder, disable and delete rules, scope a rule so it only applies to projects matching a topic or path pattern, and mark a rule not applicable for one specific project with a reason.

Cells are evaluated by server-side handlers. For file existence use List Repository Tree on the project's default branch, recursing where needed rather than guessing paths. For content rules use Get Raw File Content, which returns plain text; Get a File returns Base64, so prefer the raw variant for anything you need to read and match on. Cache each result in the app with the commit or timestamp it was checked at, so opening the board is fast and I can see when a cell was last verified. Give me a Recheck action per row, per column, and for the whole board.

The second view is a drift view. I pin one file, such as .gitlab-ci.yml or package.json, and the view lists every project alongside the value that matters from that file: the version of the shared CI template it includes, the version of a named dependency, or the pinned base image. Group identical values together so the outliers are obvious, show how many repos sit on each value, and let me change the pinned file and the value being extracted without shipping code.

Every failing cell gets a "Fix with a merge request" button that starts a background agent for that project and rule. The agent reads the current state of the file with Get Raw File Content or List Repository Tree, creates a branch off the default branch with Create a Branch, writes or corrects the file with Create a Commit using its file actions (or Create a File when the file is new), and opens a merge request against the default branch with Create a Merge Request. The merge request description should explain which standard failed, what the agent changed and why, in plain language a reviewer can check. When the agent finishes, the merge request link lands back in that cell so the board shows what is in flight, and the cell stays in an in-review state until the change is merged and the next check passes.

A "Post scorecard" action sends a weekly compliance summary to our channel with the Slack Bot Send a Message action: the overall pass rate, a score per team, which standards are failing most often, and how many fix merge requests are currently open. Let me pick the channel and preview the message before it sends.

Two rules that are not negotiable: nothing is ever committed straight to the default branch, and every fix goes through a merge request a human approves. Keep every standard file based or based on the settings Get a Project returns; do not build rules around project members, permissions or audit events, because those are not available here. Project IDs and file paths must be URL encoded in requests, so encode the slash in a namespace path and in any nested file path. Handle projects that are empty, archived, or simply missing a file without failing the whole board.