Architecture Audit

Audit project consistency across code, documentation, diagrams, and configuration files.

1|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill architecture-audit-fabioc-aloha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architecture Audit
Source: https://github.com/fabioc-aloha/AIRS_Data_Analysis/tree/main/.github/skills/architecture-audit
Command: npx skills add https://github.com/fabioc-aloha/AIRS_Data_Analysis --skill architecture-audit-fabioc-aloha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical issue of project drift, where code, documentation, and configuration become out of sync, leading to errors, maintenance nightmares, and reduced development velocity.

Core Features & Use Cases

  • Version Consistency: Verifies that version numbers are uniform across all project files (e.g., package.json, CHANGELOG.md).
  • Terminology Synchronization: Detects and helps migrate deprecated terms used within the project's codebase and documentation.
  • Fact Accuracy: Ensures that any stated counts or facts within documentation accurately reflect the current project state.
  • Diagram Validation: Checks if diagrams (Mermaid, ASCII) are up-to-date with current terminology, counts, and flows.
  • Cross-Reference Integrity: Validates that all internal links, anchor links, and image references within the project resolve correctly.
  • Code-to-Docs Sync: Confirms that code artifacts (functions, commands, errors) are accurately reflected in their corresponding documentation.
  • Configuration Alignment: Verifies that configuration files (.json, .ts) and environment variables are consistent with documentation.
  • Use Case: Before a major release, run this audit to catch any inconsistencies in versioning, outdated diagrams, or broken links that could jeopardize the release.

Quick Start

Perform a comprehensive project consistency review across code, documentation, diagrams, and configuration.

Frequently Asked Questions about Architecture Audit

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

FAQPage Schema
How do I check project consistency across code and documentation before a release?

Diagram validation checks if Mermaid and ASCII diagrams accurately reflect current terminology, counts, and flows. It ensures diagrams match the codebase and documentation, preventing outdated visual references from misleading developers.

How do I detect version drift between package.json and CHANGELOG.md?

Version drift between package.json and CHANGELOG.md is detected by running PowerShell scripts that perform pattern matching across project files. This verifies that version numbers remain uniform throughout the entire project structure.

What is code-to-documentation sync and how does an audit verify it?

Code-to-documentation sync ensures that code artifacts like functions, commands, and errors are accurately reflected in their corresponding documentation. An audit validates this by cross-referencing the codebase against the documented facts to find discrepancies.

Can I use PowerShell scripts to find broken references and deprecated terms in my project?

Yes, you can use PowerShell scripts to find broken references and deprecated terms. The scripts perform pattern matching to detect outdated terminology in the codebase and validate that internal links, anchor links, and image references resolve correctly.

Does project configuration alignment require checking environment variables against documentation?

Yes, configuration alignment requires checking environment variables and configuration files like JSON and TypeScript against documentation. Verifying this alignment prevents runtime errors caused by undocumented or mismatched settings.