---
title: "minottobot"
description: "Use whenever the user asks about QA, testing strategy, CI/CD health, team processes, developer experience, code review practices, test coverage, flaky tests, monitoring, or any audit of an engineering team's quality prac"
canonical: https://agentpluginsdirectory.com/plugins/minottobot
last-updated: 2026-10-21
---

# minottobot
Use whenever the user asks about QA, testing strategy, CI/CD health, team processes, developer experience, code review practices, test coverage, flaky tests, monitoring, or any audit of an engineering team's quality practices.
- Slug: minottobot
- Publisher: Emanuele Minotto
- Repository: https://github.com/EmanueleMinotto/minottobot
- Manifest: plugin.json
- Version: 2.6.0
- License: MIT
- Category (editorial): code-review
- Skills: 8 (audit, breaking-change-detector, daily-prevention, minottobot, reality-check, strategy, test-review, test-selection)
- MCP servers: 0
- Stars: 4
- Repository created: 2026-03-22
- Repository last pushed: 2026-09-24
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/minottobot
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What minottobot does, in the publisher's words

Your friendly neighborhood QA developer.

minottobot is a QA software consultant persona, packaged as a plugin with eight skills. It audits software teams across CI/CD, testing, monitoring, Developer Experience, and culture, then builds a prioritized improvement plan.

The repository is an Agent Plugins 1.0.0 plugin: root plugin.json, skills under skills/: and also ships the Claude Code and Codex manifests, so every client below installs it from the repo itself. No copying files around.

- Short term: immediate pain relief, quick wins
- Medium term: foundations and frameworks
- Long term: structural improvement based on feedback
- Unit: the discount/total calculation logic. Pure function, no external dependencies, fast feedback.
- Integration: cart-to-payment-service call, and the payment gateway call if a sandbox is available. This is where the interesting failure modes live (timeouts, partial charges).

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/EmanueleMinotto/minottobot/HEAD/README.md

## Skills

- audit: Use this skill to audit a software team's engineering practices, CI/CD, testing, code review, monitoring, Developer Experience, and ownership culture, and produce a scored, evidence-based audit report. Trigger when the user asks to "audit our team", "review our CI/CD setup", "assess our testing p…
- breaking-change-detector: Use this skill to help API producers and consumers find actual or potential breaking changes, REST/OpenAPI, GraphQL, gRPC/Protobuf, or consumer-driven contracts, and apply SemVer and deprecation discipline. Trigger on "will this change break our API consumers", "how do I detect breaking changes i…
- daily-prevention: Use this skill to help a developer keep day-to-day code simple, maintainable, and robust, through automatable prevention (linters, type checkers, static analysis, and, for what static analysis structurally can't catch, AI-assisted review skills) rather than after-the-fact fixes. Trigger on "how…
- minottobot: Use this skill whenever the user asks about QA, testing strategy, CI/CD health, team processes, developer experience, code review practices, test coverage, flaky tests, monitoring, or any audit of an engineering team's quality practices, and wants the full engagement, not just one half of it. Also…
- reality-check: Use this skill to give a team lead or engineering manager a fast, honest, CURRENT-STATE picture of their team or project, what's actually happening right now, pulled from live sources (issue tracker, VCS, monitoring) via MCP tools when available, or asked for directly when not. Trigger on "what's…
- strategy: Use this skill to turn an audit output into a prioritized improvement plan, executive summary, top blockers, a three-horizon roadmap, and action items. Trigger when the user pastes or already has an audit report (from the audit skill or a saved.minottobot/ snapshot) and asks "what should we do ab…
- test-review: Use this skill to review test code, not what test to write, but whether a test already written is any good. Trigger on "review this test", "is this test any good", "review my test suite", "does this test actually test what it claims", "should this be a unit test instead", or when a code review (in…
- test-selection: Use this skill when someone describes a specific code path, feature, or bug and asks what kind of test to write for it, or when an audit or strategy engagement surfaces a testing gap and needs a recommendation for where to start. Trigger on "what test should I write for this", "unit or integration…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.