THE HARNESS

One install, and the agent works like a QA Engineer.

Agent skills for Claude Code and Codex CLI, open source and running in your own terminal. Everything they do goes through the QA Vault MCP server, and nothing reaches the vault before you approve it.
qa-vault/qa-vault-skills
› install qa-vault-skills@qa-vault
✓ Plugin installed
⚙ list_projects { }
← {
  "projects": [
    { "id": 17, "code": "ACME", "title": "ACME", "archived_at": null }
  ]
}
● Ready — the vault answers. Point me at a ticket, a spec, or a suite that went red, and I’ll work from your test artifacts. Nothing is written until you approve the changeset.
›

What you install

qa-vault-skills

The plugin this page is about. Each skill knows the situation it applies to, what the vault expects of it, and where the QA Engineer stays in control.

Manual QA practiceMCP server

  • search-test-casesBefore writing anything: find what already covers a feature, by meaning rather than keywords.
  • create-test-casesA spec, ticket or conversation needs end-to-end scenarios. The agent drafts them for review.
  • maintain-test-casesA feature changed and the cases are stale. One reviewed changeset brings them back in line.
  • organize-test-repositorySuites and tags have sprawled. Restructure, merge near-duplicates, reorder.
  • backfill-search-abstractsSemantic search misses cases because their search abstracts are missing.
  • apply-lessons-learnedAn incident happened once. Find where the same class of failure can happen again.

E2E automationMCP server + Playwright

  • setup-test-automationOnce per repository: Playwright, fixtures, and the automation contract the other skills read.
  • automate-test-casesTurn approved manual cases into Playwright specs, verified against the live app and linked both ways.
  • run-automated-testsExecute the suite, separate flake from failure, record the run and its results in the vault.
  • heal-automated-testsSpecs went red. Triage each into test defect, intent change or product bug; fix only what belongs to the test.
  • reconcile-test-suiteOld specs predate the vault. Classify, link and consolidate them.
qa-vault/qa-vault-skills
ALSO IN THE QA VAULT FAMILY

Plugins for the development stage rather than the testing one. The harness does not need them, and they do not need the vault — take whichever earns its place in your repository.

codelore

Project docs as a context layer the agent consults on its own — written, indexed, and loaded before every plan, fix or investigation.

document-feature · consulting-project-docs · migrate-project-docs

needs nothing

qa-vault/codelore
quality-loop

Question the plan, test the contract, gate the PR, triage the review, and promote what holds into rules.

exploratory-qa · contract-driven-unit-tests · contract-driven-integration-tests · setup-quality-loop · run-quality-gate · triage-code-review · promote-quality-rules

needs Semgrep CE · Greptile for the review legs

qa-vault/quality-loop