quality-supervisor

Plugin quality-supervisor from marketplace quality-supervisor in qase-tms/qase-quality-supervisor. Commands read from the repo's manifest — 9 days ago.

Skills (7)

• analyzing-change-impact

  Analyze what a feature branch changes and produce a QA-facing impact analysis plus a regression/new checklist, grounded in the project's existing Qase cases. Use when the user asks for an impact analysis, change impact, risk analysis, or blast radius of a branch or PR; what QA should test for these

• analyzing-test-coverage

  Find where a Qase project's test coverage is thin. Use when the user asks about test coverage or coverage gaps; what isn't tested, untested areas, or what is missing tests; which cases are still manual, not automated, or yet to be automated; which cases have never been run or executed; which suites

• analyzing-test-flakiness

  Find genuinely flaky tests in a Qase project — cases that both pass and fail — and separate them from tests that are simply broken. Use when the user asks which tests are flaky, unreliable, unstable, intermittent, or non-deterministic; about test stability, flakiness, or the flake rate; which tests

• assessing-release-readiness

  Produce an evidence-backed go / no-go assessment for a Qase release scope — a milestone, a test plan, or a set of runs. Use when the user asks whether they are ready to ship, release, or cut a version; for a go/no-go, a release sign-off, or a quality gate; what is blocking the release or holding it

• linking-test-cases

  Link a repository's autotests to Qase test cases by meaning: propose a mapping for confirmation, write the confirmed case IDs into the test code in each Qase reporter's own syntax, and mark the linked cases Automated. Use when the user asks to link, map, match, or connect autotests or automated test

• reporting-quality-pulse

  Build a visual "Quality Pulse" report card for a Qase project over any period the user chooses — daily, weekly, biweekly, monthly, sprint, or a custom date range. A styled HTML card summarizing test execution, pass rate, defect backlog, case activity, and active users for that window. Use this whene

• triaging-test-failures

  Triage the failures in a Qase test run: cluster them by error signature, separate real product bugs from automation, environment, and flaky noise, and file defects. Use when the user asks to triage a run; why a run, a build, or the tests in it failed; why last night's or the latest run failed or is

Slash commands (1)

• /quality-supervisor:quality-report

  Run a full Quality Supervisor sweep on a Qase project and produce a consolidated quality report.

Subagents (1)

• quality-supervisor

  Autonomous QA quality supervisor for Qase. Routes quality questions to the right analysis — coverage gaps, failure triage, flakiness, or release readiness — and produces evidence-backed reports. Invoke when the user asks broad quality questions like "how healthy is our testing," "supervise quality f

MCP servers (1)

• qase

  connects to: https://mcp.qase.io/mcp

Hooks (4)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/deny-destructive.sh"

• PreToolUse

  powershell.exe

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/deny-destructive-api.sh"

• PreToolUse

  powershell.exe

Similar plugins