YannRobert

Mr Dashboard — Testing skill for Claude Code

Testing community

How to install Mr Dashboard

This entry records only its repository, not the path inside it, so there is no exact command to give. Open YannRobert/mr-dashboard and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Mr Dashboard does

The development workflow of GitLab merge requests on one page, for authors and reviewers: pipeline, SonarQube, mutation testing and review signals of every open MR, a diff viewer where you comment and resolve threads, browser notifications, and one-click AI prompts. Made for agentic development, without an IDE. Runs on your machine.

Alternatives in Testing

Pua — Use when the user invokes /pua or asks for PUA mode, try-harder/retry help, change-approach coaching, completi 19.5k ★
Spec Kitty — Spec-Driven Development for serious software developers 1.6k ★
Spec Draft PR — Turn a feature idea or GitHub issue into a one-page spec saved to Documentation/specs/ and opened as a draft P 324 ★

README

MisteR Dashboard

Created and maintained by [Yann ROBERT](https://github.com/YannRobert) · Website:

[![MisteR Dashboard listing the open merge requests of a project, each with its commits, comments, unresolved threads, pipeline, Sonar issues, coverage, remaining mutants and lag behind the target branch.](https://yannrobert.github.io/mr-dashboard/tour/dashboard.png)](https://yannrobert.github.io/mr-dashboard/)

*The open merge requests of the demo project, an invented online bookshop: [take the tour](https://yannrobert.github.io/mr-dashboard/tour.html), or [try it](#try-it-without-a-gitlab) without a GitLab.*

A local dashboard for the development workflow of a GitLab project's merge requests, from the first push to the merge, for authors and reviewers alike. Each open merge request shows its CI signals (pipeline, SonarQube, mutation testing, unresolved threads, lag behind the target branch) and its review activity: commits, comments, who pushed or commented last.

Authors see what is left to do on their merge requests: a failed pipeline, a quality gate, a mutation score, the threads to answer.
Reviewers see which merge request is ready for them, and read only what changed since their last review.
Browser notifications tell you when your merge request breaks or gets approved, and when the main branch's pipeline fails.

It also offers a diff viewer built on the local git clone, where threads are opened, answered and resolved, a comments page, and an **AI** button that prepares prompts for a merge request, for Claude Code, Codex or Pi.

Made for agentic development, where coding agents write the code across several worktrees and nobody keeps an IDE open on each of them. The diff of every merge request comes from the local git clone, without checking anything out, so neither the author nor the reviewer opens an IDE to read it. The **AI** button turns the fix of what is red, and the actions the project defines,