Comprehensive **project** consistency review across code, documentation, diagrams, and configuration
tier
standard
applyTo
**/*audit*,**/*review*,**/*consistency*
Architecture Audit
Comprehensive project consistency review across code, documentation, diagrams, and configuration
Overview
Systematic audit process to ensure all project artifacts stay synchronized. Catches version drift, terminology inconsistencies, outdated diagrams, broken references, and code-to-docs mismatches.
⚠️ IMPORTANT: This skill audits the user's project code, NOT the Alex cognitive architecture in .github/. Ignore .github/ folder contents when performing audits - focus on the actual source code, documentation, and configuration in the project root and subdirectories.
Triggers
"audit", "comprehensive review", "fact-check"
"consistency check", "project health"
"pre-release audit", "documentation review"
Before major releases or after significant refactoring
Audit Checklist
1. Version Consistency
# Find version references in common locations
# EXCLUDE: .github/** (Alex cognitive architecture - not project code)
$patterns = @(
'package.json', # "version": "x.y.z"
'src/**/config*.json', # Version in config files (not .github)
'*.md', # Root documentation only
'docs/**/*.md', # Project docs (not .github)
'src/**/constants.ts', # Hardcoded versions
'CHANGELOG.md' # Version headers
)
# Grep for version patterns
Get-ChildItem -Recurse -Include $patterns |
Select-String -Pattern 'v?\d+\.\d+\.\d+' |
Group-Object -Property Line
Check: All version references match the canonical version (usually package.json)
# Weekly full auditon:schedule:-cron:'0 9 * * 1'# Monday 9am
Anti-Patterns
❌ Skipping audits before release — Drift accumulates silently
❌ Manual-only audits — Automate what you can
❌ Fixing without documenting — Record the pattern for next time
❌ Ignoring "cosmetic" issues — They signal deeper drift
❌ Auditing only changed files — Drift affects unchanged files too
Best Practices
✅ Run full audit before major releases
✅ Add new deprecated terms as you migrate
✅ Update fact inventory after structural changes
✅ Document audit findings for patterns
✅ Automate repetitive checks
✅ Time-box manual review (don't boil the ocean)
Integration with Other Skills
release-preflight → Trigger audit before release
brain-qa → Synapse-specific validation and architecture health
code-review → Audit as part of PR review
refactoring-patterns → Audit after major refactoring
Master Alex Extensions
Master Alex-specific audit procedures that extend the generic project audit above. These leverage knowledge of exact folder structure, heir relationships, safety imperatives, and build/release workflows.