mcpField
T
testdino-audit

testdino-audit

github.com/anthropicsTesting & quality4.8k49 installsUpdated 2w ago
Repository

About testdino-audit

TestDino Audit is a skill for auditing Playwright automated test code, used only when a TestDino audit is explicitly requested. It retrieves audit context, prepares a local report, submits it, and can retrieve previous audits.

Key features

  1. 01Runs only for explicit TestDino audit requests
  2. 02Targets Playwright automated test code
  3. 03Fetches context before writing findings
  4. 04Submits and retrieves audit reports
  5. 05Selects from tools exposed by the server

Use cases

  1. 01Review Playwright automated tests
  2. 02Submit a score and Markdown audit report
  3. 03Browse or retrieve previously submitted audits

MCP support

Works with the TestDino MCP server to fetch audit context, submit reports, and retrieve audit history using the tools it exposes.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/anthropics/claude-plugins-community --skill testdino-audit

After installing, type/testdino-auditin Claude Code to confirm it loaded.

Details

From the project README

TestDino Audit

Use the TestDino audit flow only when the user explicitly asks for a TestDino audit.

Rules:

  • If the user asks for a generic review or audit, do a normal review in chat.
  • If the user explicitly asks for a TestDino audit and the target is Playwright code, use the audit tools below.
  • If the user names TestDino but the target is not Playwright code, explain that the TestDino audit flow is for Playwright automated tests and offer a normal review instead.

Tool selection — use whichever audit tools the TestDino MCP server exposes:

  • If get_audit_report and submit_audit_report are available, prefer those (the current split tools).
  • If only the legacy test_audit tool is available, use it instead (it takes an action parameter).
  • Do not invent a tool that is not in the available tool list.

Preferred flow:

  1. Call health if projectId is not known.
  2. Fetch the audit context (read-only). Do not write findings, score, or headings before this returns.
    • New tools: get_audit_report with action: "context".
    • Legacy: test_audit with action: "analyze" and no score.
  3. Review the local Playwright target using the returned context and write findings to a local markdown file (e.g. TEST-AUDIT.md).
  4. Submit the completed report (score + markdown report).
    • New tools: submit_audit_report.
    • Legacy: test_audit with action: "analyze" plus score and markdownReport.
  5. Browse or retrieve previously submitted audits.
    • New tools: get_audit_report with action: "list" or action: "get".
    • Legacy: test_audit with action: "list" or action: "get".

Important:

  • keep generic reviews as normal chat reviews
  • use the TestDino audit flow only for explicit TestDino audit requests
  • keep this flow centered on Playwright automated test code

Comments

Markdown supported