sumo-qa 0.1.2

Sumo QA — a senior-QA-shaped MCP server for pre-coding QA planning, TDD scaffolding, mutation-testing follow-up, code review, and test-data discovery.

sumo-qa MCP

A senior-QA MCP server + skills library that delivers ISTQB-grade testing discipline to AI coding agents across Claude Code, Cursor, Codex, OpenCode, JetBrains AI Assistant + Junie, and VS Code + GitHub Copilot. The discipline lives in skill files the host LLM follows literally; MCP tools provide canonical knowledge catalogues; a SessionStart hook auto-injects the using-sumo-qa router so the agent reliably runs the workflow without you having to remember to invoke it.

🚀 New here? 5-minute demo →

Install with one line, run one prompt on your real repo, see the senior-QA workflow happen on actual code. No staged data, no scripted output.

Why sumo-qa?

Most AI coding assistants approach QA the way a junior engineer would: "add unit tests, consider edge cases, maybe test performance too." That's a checklist, not testing. sumo-qa makes the AI work like a senior QA — risks named against specific lines, design techniques (boundary-value, decision-table, property-based, mutation) picked from a loaded ISTQB-grounded catalogue, test suites run fresh in this turn before any "safe to merge" claim.

The discipline is enforced by 13 skill files the host LLM follows literally — each one with an Iron Law (TDD's red phase before any production code; mutation-strengthening keeps production code locked; no plan ships without measurable entry AND exit criteria) and a HARD-GATE callout the LLM can't talk itself past. A SessionStart hook auto-injects the entry router on every conversation, so the workflow kicks in without you having to remember to invoke it.

Read DEMO.md for the 5-minute install-and-run-this-prompt walkthrough.

Install

One-line install (PyPI)

pip install sumo-qa
# or:  uv tool install sumo-qa

After install, restart your MCP host (Claude Code / Cursor / Codex / OpenCode / JetBrains AI Assistant / VS Code + Copilot) so it picks up the new MCP server.

Claude Code plugin

/plugin marketplace add sumithr/sumo-qa
/plugin install sumo-qa@sumo-qa-dev

Then uv tool install sumo-qa (or pip install sumo-qa) so the MCP server binary is on PATH. The skills come from the plugin; the MCP tools come from the binary.

Multi-host batch install (JetBrains + VS Code + everywhere)

python3 install.py

Configures every supported host detected on this machine. Per-host flags + troubleshooting in docs/INSTALL.md.

From a git URL (latest main)

uv tool install --from git+https://github.com/sumithr/sumo-qa.git sumo-qa

What you get

Layer	What it is
13 skills (skills/*/SKILL.md)	Iron-Law-enforced procedures the host LLM follows. Cover deciding approach, preparing for work, scaffolding TDD, reviewing diffs, strengthening tests, finding test data, answering testing questions, repo-wide strategising — plus planning + subagent execution + finishing chain (planning → dispatch parallel subagents → capture evidence + PR-ready summary).
24 MCP entry points	13 skill tools + 7 knowledge loaders + 4 test-data tools. Thin file IO; no inference.
5 knowledge catalogues (knowledge/*.md)	4 authoritative catalogues (classifications, approaches, principles, techniques) — the LLM picks from these, not from training-data recall. Plus 1 category-fit primer (specialty_tools) where the LLM picks tool brands from its training knowledge and the file confirms the category fits. Editable as plain markdown.

Host support

Each host surfaces the same skills and tools differently — that's a host-API difference, not a sumo-qa choice. All routes call the same MCP server and read the same SKILL.md content.

Host	Slash invocation	Setup
Claude Code	/qa-deciding-approach (hyphens)	Native plugin: /plugin marketplace add sumithr/sumo-qa then /plugin install sumo-qa@sumo-qa-dev. Or install.py --claude-code.
Cursor	Natural language; Cursor picks skills by description	Native plugin: /add-plugin sumo-qa
Codex	Natural language; Codex picks skills by description	Codex plugin marketplace (search "Sumo QA")
OpenCode	skill tool (use skill tool to load sumo-qa/...)	Add "sumo-qa@git+..." to opencode.json plugin array, restart
JetBrains AI Assistant	/qa_deciding_approach (underscores)	One-time Settings → Tools → AI Assistant → Model Context Protocol → Add server with absolute binary path. install.py --jetbrains prints the fields to paste.
JetBrains Junie	Natural language; Junie picks tools by description	Drop the JSON install.py prints into ~/.junie/mcp/sumo-qa.json (global) or <repo>/.junie/mcp/ (per-project)
VS Code + Copilot (Agent mode, Claude Sonnet 4.5 or equivalent)	Natural language; Copilot picks tools by description	install.py --vscode --workspace <repo> writes <repo>/.vscode/mcp.json

In Claude Code, MCP tools are NOT slash-invocable directly — use natural language (e.g. "load the QA classifications") and the AI picks the right tool. In JetBrains AI Assistant, every tool IS slash-invocable. Both paths work; both end up calling the same skill body.

Quick test in any host: ask in chat "load the QA classifications". Should return 10 names: api_contract_change, business_logic_change, security_change, performance_change, frontend_change, infrastructure_change, test_change, docs_change, config_change, data_migration. If yes, you're wired correctly.

See it in action

Ten polished worked examples showing what sumo-qa actually looks like in conversation — diff reviews refusing to declare safe-to-merge, TDD cycles with the red output surfaced verbatim, mutation survivors walked one-at-a-time, formal test plans gated on measurable entry/exit criteria, and the surprising one where it correctly says "no tests needed" and stops:

• tests/scenarios/worked-examples/ — see 02 — review-my-changes for a representative end-to-end transcript.
• tests/scenarios/SCENARIOS.md — the underlying scenario specs (user prompt → expected interaction shape → anti-patterns the skill prevents).

License

Licensed under the Apache License, Version 2.0. See NOTICE for attribution requirements that apply to forks and redistributors.

Docs

• AGENTS.md — AI-agent bootstrap and per-host setup
• docs/ARCHITECTURE.md — three layers, host delivery, knowledge authority
• docs/SKILLS.md — the 13 skills with their Iron Laws
• docs/TOOLS.md — the 24 MCP entry points
• docs/INSTALL.md — per-host install detail, schema differences, troubleshooting
• docs/CONFIGURATION.md — env vars
• docs/DEVELOPMENT.md — local dev
• docs/TEST-DATA.md — known-good test-data catalogue
• docs/superpowers/ — design spec, implementation plans, iteration history