qa-agent

Plugin qa-agent from marketplace devops-qa-agent in GhassenAZZOUZ/claude-qa-agent. Commands read from the repo's manifest — 6 days ago.

Skills (31)

• api-session

  WAY 2 — API test session. Use when the user says "api it", "test api", "run api tests", "api test" — OpenAPI spec or endpoint list → playwright-bdd API tests → run → file bugs → API session report.

• benchmark

  WAY 7 — competitor benchmark. Use when the user says "benchmark it", "find competitors", "compare apps", "find alternatives" for an app URL, name, or Git repo.

• bug-report

  Classify a bug's severity × priority and format a developer-ready issue body for it (any tracker) — from a failed test (WAY 1 Phase 4, WAY 2 Phase 3) or from the WAY 3 quick-report shorthand ("report it", "log this", "raise this", "file this issue"). Replaces the former severity-classifier and bug-r

• ci-test-setup

  WAY 10 — make the generated playwright-bdd suites run in CI on every MR/PR, on the default branch, and on schedules, without Claude — GitLab CI, GitHub Actions, Azure Pipelines, or Bitbucket Pipelines. Use when the user says "ci setup", "add tests to ci", "run tests in pipeline", "set up qa pipeline

• diagnose-ci

  WAY 5 — diagnose a failed CI run (GitLab pipeline, GitHub Actions run, Azure Pipelines run, Bitbucket pipeline). Use when the user says "ci it", "diagnose ci", "fix ci", "why did ci fail", "check pipeline" with a run URL or ID.

• e2e-session

  WAY 1 — full UI E2E (browser) session. Use when the user says "e2e it", "test it", "run e2e", "start testing", "qa this" — requirements (text or a tracker issue) or an approved test plan → plan approved → Gherkin/playwright-bdd tests → run → heal or file bugs → session report.

• enhance-story

  WAY 6 — score and rewrite a user story in your tracker (GitLab, GitHub, Jira, Azure Boards). Use when the user says "analyze us", "enhance us", "analyze and update us", "improve us" with an issue ref (#143, SHOP-143).

• explore-session

  WAY 18 — exploratory testing session, no requirements needed. Use when the user says "explore it", "exploratory test", "explore the app", "bug hunt", "exploratory session" — charter → live browser exploration → test-writer turns the flows and anomalies into playwright-bdd tests → run now or later (`

• flaky-triage

  WAY 13 — find flaky tests across recent runs and quarantine them so they stop producing false bug reports. Use when the user says "flaky", "find flaky tests", "triage flaky", "quarantine", or after repeated unexplained failures.

• gap-stories

  WAY 8 — turn a competitor benchmark into user stories. Use when the user says "gap it", "stories from benchmark", "match the leader", "write gap stories", or chains "benchmark it <target> then gap it".

• heal-tests

  WAY 16 — repair tests broken by UI changes (renamed buttons, moved elements) from the latest run. Use when the user says "heal it", "heal tests", "fix selectors", "tests broke after the redesign".

• integration-tests

  WAY 17 — write API integration tests (one OpenAPI spec) or E2E API tests (several specs, one per service), no execution. Use when the user says "integration it", "write integration tests", "integration tests from spec", "generate integration tests", "e2e api it", "write e2e api tests", "multi-servic

• load-test

  WAY 15 — API load / stress / spike / soak testing with k6. Use when the user says "load test", "stress test", "perf test the api", "how many users can it handle", "spike test".

• mr-impact

  WAY 11 — run only the tests a merge request / pull request puts at risk and report on it (GitLab MR, GitHub PR, Azure DevOps PR, Bitbucket PR). Use when the user says "test mr", "test pr", "mr impact", "pr impact", "what does !87 break", "check this pr" with an MR/PR number or URL.

• provider-azure-devops

  How to perform the tracker skill's operations on Azure DevOps (Services or Server) — Boards work items, Repos pull requests, Pipelines runs and logs, attachments — with the az CLI (azure-devops extension) and its REST API. REST calls were checked against Microsoft's 7.1 reference. Load it when QA_TR

• provider-bitbucket

  How to perform the tracker skill's code-host operations on Bitbucket Cloud — pull requests, diffs, PR comments, Pipelines runs and step logs — through the Bitbucket REST API. Bitbucket is a code host here; pair it with Jira (or another tracker) for issues. Load it when QA_CODE_HOST is bitbucket.

• provider-github

  How to perform the tracker skill's operations on GitHub (github.com or GitHub Enterprise) with the gh CLI — issues, pull requests, Actions workflow runs and logs, labels, attachments. Every write and CI path was run live against a test repo. Load it when QA_TRACKER or QA_CODE_HOST is github.

• provider-gitlab

  How to perform the tracker skill's operations on GitLab (gitlab.com or self-hosted) through the bundled GitLab MCP server — issues, merge requests, pipelines, CI lint, uploads. Load it when QA_TRACKER or QA_CODE_HOST is gitlab.

• provider-jira

  How to perform the tracker skill's issue operations on Jira (Cloud or Data Center) — create, update, comment, transition, search, attach — through the Atlassian MCP server if connected, otherwise the Jira REST API. Jira is a tracker only; pair it with a code host (GitHub, GitLab, Azure DevOps, Bitbu

• qa-setup

  WAY 0 — prepare the current project for DevOps QA Agent — test runner in qa-artifacts/, issue tracker and code host (GitLab, GitHub, Jira, Azure DevOps, Bitbucket), per-project .env values, access check. Use when the user says "qa setup", "set up qa", "init qa agent", or when another WAY finds qa-ar

• quick-bug

  WAY 3 — quick bug report from a one-line description. Use when the user says "report it", "log this", "raise this", "file this issue" with input like "[Area], [Precondition], [Step 1 > Step 2 > Observe: what you saw]". Files the bug and writes a regression test for it.

• release-readiness

  WAY 12 — go / no-go report for a release or milestone. Use when the user says "release check", "go no go", "are we ready to release", "release readiness" with a milestone or version.

• requirements-analysis

  Reference only — the single definition of how requirements are analyzed before tests or stories are written — intake (text, issue, enhanced story, spec, exploration session, approved test plan) into one requirements model, the readiness gate (Missing Information, vague wording), requirement IDs (AC-

• review-plan

  WAY 20 — independent review of a test plan before it's approved. Use when the user says "review plan", "review the plan", "review test plan", "plan review", "improve the plan" with a plan ref or path. Scores the plan out of 100 with evidence, proposes test cases to add, remove, merge or modify (each

• session-report

  Produce, save, and file the end-of-session QA summary for a WAY 1 (browser) or WAY 2 (API) run — execution counts, failed test cases, accessibility table (WAY 1), schema/performance flags (WAY 2), bugs filed. Replaces the former session-reporter agent.

• test-plan

  WAY 19 — design a test plan before any test code. Use when the user says "plan it", "plan tests", "test plan", "design tests" with requirements (text or a tracker issue), optional App/Spec/MR or PR. Output is the test plan (scope, levels, one row per Test#<nn> with category, tags, covers, priority,

• traceability

  WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says "trace it", "traceability", "is #148 covered", "coverage of SHOP-1

• tracker

  Provider-neutral contract for every issue-tracker and code-host action (create/update/comment/close issues, attach files, comment on MRs/PRs, read CI runs and logs) plus label conventions and failure handling. Every WAY calls these operations; the matching provider-* skill says how to perform them o

• user-story-format

  Reference only — the single definition of this project's user-story body (story, Gherkin ACs, Missing Information, DoD) and its AC/scenario rules. Read by user-story-enhancer (WAY 6) and benchmark-gap-story-writer (WAY 8) so stories they write stay identical in shape and WAY 6 can re-score WAY 8's o

• verify-fix

  WAY 9 — verify that a bug is fixed by running its regression test. Use when the user says "verify it", "verify fix", "is #142 fixed", "check the fix" with one or more bug refs (#142, SHOP-142), or "verify all" for every open bug that has a regression test.

• write-tests

  WAY 4 — write test cases only, no execution. Use when the user says "write it", "write tests", "generate test cases" — an approved test plan (`Plan:`), or requirements (text or a tracker issue) planned and approved first, optional App/Spec/MR or PR → exactly the planned test files.

MCP servers (2)

• gitlab

  runs: npx -y @zereight/[email protected]

• playwright

  runs: npx -y @playwright/[email protected] --headless --isolated --output-dir qa-artifacts/explore/.mcp

Hooks (1)

• SessionStart

  node

Similar plugins