一键导入
qa-diagram-generator
Universal diagram generator supporting 14 Mermaid diagram types. Works standalone or as an embedded service for other QA skills.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Universal diagram generator supporting 14 Mermaid diagram types. Works standalone or as an embedded service for other QA skills.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | qa-diagram-generator |
| description | Universal diagram generator supporting 14 Mermaid diagram types. Works standalone or as an embedded service for other QA skills. |
| output_dir | docs/diagrams |
Universal diagram generator for the QA skills ecosystem. Works in two modes:
| Mode | Trigger | Output |
|---|---|---|
| Standalone | User: "Draw a sequence diagram for API auth flow" | Full Mermaid diagram + explanation |
| Embedded | qa-spec-writer needs state diagram for spec | Reference references/state-diagram.md + generate inline |
When embedded, the calling skill references the appropriate references/*.md file and generates Mermaid code following those patterns.
| Type | Use Cases | Mermaid Syntax | Reference |
|---|---|---|---|
| Flowchart | Test process flows, decision trees, regression flow | flowchart | references/flowchart.md |
| Sequence Diagram | API interactions, login flow, test execution flow | sequenceDiagram | references/sequence.md |
| Class Diagram | Test architecture, Page Object Model | classDiagram | references/class-diagram.md |
| State Diagram | Bug lifecycle, test case states, user session states | stateDiagram-v2 | references/state-diagram.md |
| ER Diagram | Test data models, database schemas | erDiagram | references/er-diagram.md |
| Mind Map | Test coverage mapping, feature decomposition | mindmap | references/mindmap.md |
| Gantt Chart | Test schedules, sprint planning, release timelines | gantt | references/gantt.md |
| C4 Model | System architecture (context/container/component) | C4Context, C4Container, C4Component | references/c4-model.md |
| User Journey | User experience testing flows, E2E scenarios | journey | references/journey.md |
| Pie Chart | Test result distribution, coverage breakdown | pie | references/charts.md |
| Quadrant Chart | Risk matrix, priority vs effort, impact vs likelihood | quadrantChart | references/charts.md |
| Git Graph | Branch strategy, release flow, merge workflows | gitGraph | references/flowchart.md (see note) |
| Block Diagram | System components, data flow blocks | block-beta | references/flowchart.md |
| BPMN | Business process flows, approval workflows | bpmn | references/flowchart.md |
When another skill needs a diagram, reference the appropriate file:
| Visualization Need | Reference | Example |
|---|---|---|
| State machines, lifecycle | references/state-diagram.md | Bug lifecycle, test case states |
| API flows, interactions | references/sequence.md | Login flow, API contract validation |
| Decision logic, process flow | references/flowchart.md | Test process, regression flow |
| Timelines, schedules | references/gantt.md | Sprint plan, release schedule |
| Architecture layers | references/c4-model.md | System context, container diagram |
| Test data structure | references/er-diagram.md | Test DB schema, fixture models |
| Coverage/feature breakdown | references/mindmap.md | Test coverage map, feature tree |
| User flows, E2E scenarios | references/journey.md | UAT journey, UX test flow |
| Result distribution, risk | references/charts.md | Pass/fail pie, risk quadrant |
| From screenshot/image | references/from-screenshot.md | UI → flowchart, whiteboard → diagram |
Can do (autonomous):
Cannot do (requires confirmation):
Will not do (out of scope):
| Symptom | Likely Cause | Fix |
|---|---|---|
| Mermaid parse error | Invalid syntax, reserved keywords | Check reference syntax; escape special chars |
| Wrong diagram type | Ambiguous input | Ask user or infer from dominant structure (flow vs state vs sequence) |
| Too complex | Too many nodes/edges | Split into multiple diagrams or simplify |
| Embedded skill gets wrong ref | Mismatch between need and ref | Use embedding table to map visualization need → reference |
| Screenshot analysis fails | Low quality or non-diagram image | Fall back to text description; ask user to describe |
| C4/ER syntax errors | Mermaid version differences | Use standard syntax from references; avoid experimental features |
Master skill coordinating all QA skills through pipeline modes (full-cycle, docs-only, testcases-only, write-tests, report), formalized handoff chains, scheduler rules, and framework/language selection based on project context.
QA project memory with auto-update. Structured log of bugs, decisions, tests, regressions, environments. Automatically updated after every QA task. Archive system with searchable index for large projects. Trigger phrases (EN): "initialize memory", "init qa memory", "find known bug", "search memory", "show what was done", "check regressions", "memory status", "archive memory", "log a bug", "add decision", "memory summary", "what bugs do we know", "update memory", "show test log". Trigger phrases (UA): "ініціалізувати пам'ять", "знайти відомий баг", "пошук у пам'яті", "показати що було зроблено", "перевірити регресії", "статус пам'яті", "архівувати пам'ять", "залогувати баг", "додати рішення", "зведення пам'яті", "які баги відомі", "оновити пам'ять", "показати лог тестів", "що ми вирішили про", "які тестові середовища є".
Analyze OpenAPI/Swagger spec (JSON or YAML) against existing test files and generate an HTML coverage report with QA automation tasks. Use when user provides an OpenAPI spec file and wants to know test coverage status.
Generate accessibility tests for WCAG 2.2 compliance using axe-core, Pa11y, and Lighthouse with automated checks for ARIA patterns, keyboard navigation, color contrast, and screen reader support.
Manage and formalize API contracts from existing endpoints, swagger/JSON, network traffic, or developer interviews into OpenAPI specifications.
Autonomously explore live web applications using Playwright MCP to collect page structure, form fields, validation rules, API endpoints, and user flows for test case generation.