reviewing-diagrams

Review Mermaid diagrams and Excalidraw conversion code for correctness and best practices.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/meriley/claude-code-skills --skill reviewing-diagrams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-diagrams
Source: https://github.com/meriley/claude-code-skills/tree/main/skills/reviewing-diagrams
Command: npx skills add https://github.com/meriley/claude-code-skills --skill reviewing-diagrams

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that Mermaid diagrams and their Excalidraw conversions meet high standards for correctness, clarity, and compatibility, preventing errors and improving understanding.

Core Features & Use Cases

  • Diagram Validation: Checks Mermaid syntax, node IDs, subgraph usage, and diagram clarity.
  • Excalidraw Compatibility: Verifies Excalidraw conversion code, import paths, and .excalidraw file structure.
  • Severity Reporting: Categorizes issues from critical (P0) to low (P3) with actionable fixes.
  • Use Case: When reviewing a pull request that introduces a new system architecture diagram in Mermaid format, use this skill to automatically flag any syntax errors, unclear labels, or potential conversion issues before merging.

Quick Start

Review the Mermaid diagram in the file 'architecture.md' for correctness and clarity.

Frequently Asked Questions about reviewing-diagrams

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Mermaid diagrams for syntax errors and unclear node labels?

Mermaid diagram validation checks syntax correctness, node IDs, subgraph usage, and label clarity to detect structural anti-patterns. It categorizes issues by severity from P0 to P3 with actionable fixes.

Can I check if my Mermaid diagram has unsupported shapes for Excalidraw conversion?

Excalidraw conversion checks your Mermaid diagrams for unsupported shapes. It verifies conversion code, import paths, and .excalidraw file structure to prevent integration errors.

What is the best way to audit diagram quality in a pull request?

Auditing diagram quality in pull requests involves reviewing Mermaid syntax and Excalidraw conversion code for correctness and clarity. This flags syntax errors, unclear labels, and missing error handling before merging.

How do I fix missing error handling in Mermaid-to-Excalidraw integration code?

Fixing missing error handling in Mermaid-to-Excalidraw integration requires validating import paths and .excalidraw file structure. Diagram review identifies these gaps and reports them with actionable fixes.

What are common structural anti-patterns to look for when reviewing diagrams?

Common structural anti-patterns when reviewing diagrams include unsupported Excalidraw conversion shapes, unclear node labels, and missing error handling. Diagram validation detects these and categorizes them by severity.