verify-diag

Validate architecture diagrams against source code for component and connection accuracy.

5|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill verify-diag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-diag
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/.claude/skills/verify-diag
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill verify-diag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that architecture diagrams accurately reflect the actual codebase, preventing discrepancies and improving documentation reliability.

Core Features & Use Cases

  • Component Verification: Checks if all components shown in a diagram exist in the codebase.
  • Connection Accuracy: Traces actual code paths to validate connections and their directionality (read/write).
  • Use Case: After generating an architecture diagram for a new feature, use this Skill to confirm that all depicted modules and their interactions are correctly implemented in the source code.

Quick Start

Use the verify-diag skill to check the accuracy of the attached diagram 'service-flow.mmd'.

Frequently Asked Questions about verify-diag

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

FAQPage Schema
How do I validate a Mermaid architecture diagram against my source codebase?

Validating a Mermaid diagram involves checking component existence, tracing actual code paths to confirm connection accuracy, and verifying read/write directionality to ensure semantic and structural alignment between the diagram and the codebase.

What is architecture diagram verification and why is it needed for software reviews?

Architecture diagram verification ensures that depicted modules and their interactions are correctly implemented in the source code, preventing discrepancies and improving documentation reliability during software architecture reviews.

Can I check if all components shown in a diagram actually exist in the codebase?

Yes, component verification checks if all components shown in a diagram actually exist in the codebase by parsing diagram definitions and validating them against the actual source code structure.

How do I trace code paths to verify connection directionality in architecture diagrams?

To verify connection directionality, trace actual code paths within the codebase to validate that the read and write interactions depicted in the architecture diagram match the implemented logic.

Does architecture diagram validation work for documentation integrity checks?

Architecture diagram validation works for documentation integrity checks by verifying component existence and connection accuracy, ensuring that architecture diagrams accurately reflect the actual codebase and preventing structural discrepancies.

What are the limitations of validating architecture diagrams against source code?

Limitations of validating architecture diagrams against source code include the complexity of parsing diagram definitions and analyzing the codebase comprehensively to ensure full semantic and structural alignment without encountering incomplete traces.